Triple
T36709991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWiFS |
E906768
|
entity |
| Predicate | hostSatelliteFamily |
P187010
|
FINISHED |
| Object | Resourcesat 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: Resourcesat series | Statement: [AWiFS, hostSatelliteFamily, Resourcesat series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSatelliteFamily Context triple: [AWiFS, hostSatelliteFamily, Resourcesat series]
-
A.
hostSatelliteInstanceOf
Indicates that a host satellite is an instance of a specified satellite type, class, or model.
-
B.
hostSatelliteFullName
Indicates that one entity is the full official name of the satellite that serves as the host in a given satellite–host relationship.
-
C.
hostSatelliteMission
Indicates that an entity organizes, manages, or provides the platform and infrastructure for a satellite mission.
-
D.
hostFamily
Indicates that one entity serves as a host family, providing accommodation, care, or support to another entity, typically for a temporary or exchange-based stay.
-
E.
hostOrbit
Indicates that one celestial body orbits around another body that serves as its primary gravitational host.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.