Triple
T8083035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mengtian |
E188662
|
entity |
| Predicate | supportsEarthObservationInstruments |
P37032
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mengtian, supportsEarthObservationInstruments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEarthObservationInstruments Context triple: [Mengtian, supportsEarthObservationInstruments, yes]
-
A.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
B.
instrumentsOnOrbiter
chosen
Indicates that certain scientific instruments are mounted on and operate from an orbiting spacecraft.
-
C.
usedWithSpacecraft
Indicates that something is employed or operated in conjunction with a spacecraft.
-
D.
supportsObservationModes
Indicates that one entity provides or is compatible with specific modes or methods of observation used by another entity.
-
E.
hasRemoteSensingDataFrom
Indicates that one entity possesses or is associated with remote sensing data that was obtained from another entity or source.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415cb4688190920868317e77bbff |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.