Triple
T36487329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LISS-I |
E898966
|
entity |
| Predicate | missionFamily |
P189755
|
FINISHED |
| Object | IRS-1 series |
—
|
NE NERFINISHED |
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: IRS-1 series | Statement: [LISS-I, missionFamily, IRS-1 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionFamily Context triple: [LISS-I, missionFamily, IRS-1 series]
-
A.
fareFamily
Indicates a relationship that classifies a fare or ticket into a specific fare family or category within a pricing structure.
-
B.
enemyFamily
Indicates that two entities belong to families that are hostile or in conflict with each other.
-
C.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
-
D.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
E.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
- F. None of above. chosen
Provenance (4 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_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:10 p.m.