Triple
T36487196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LISS-I sensor |
E898963
|
entity |
| Predicate | typicalRevisitPeriod |
P7618
|
FINISHED |
| Object | 22 days (IRS-1A/1B) |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 22 days (IRS-1A/1B) | Statement: [LISS-I sensor, typicalRevisitPeriod, 22 days (IRS-1A/1B)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRevisitPeriod Context triple: [LISS-I sensor, typicalRevisitPeriod, 22 days (IRS-1A/1B)]
-
A.
typicalReEntryPeriod
Indicates the usual or standard amount of time that typically passes before something returns, reoccurs, or re-enters a given state, context, or system.
-
B.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
C.
typicalExpirationPeriod
Indicates the usual length of time after which something is expected to expire or become invalid.
-
D.
typicalPeriodRange
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
E.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.