Triple
T5497751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Telescope Mount |
E144251
|
entity |
| Predicate | crewOperated |
P65080
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Apollo Telescope Mount, crewOperated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewOperated Context triple: [Apollo Telescope Mount, crewOperated, true]
-
A.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
operatesVessel
Indicates that an agent is responsible for controlling, managing, or running the operation of a vessel.
-
C.
operatedBehind
Indicates that one entity performed an operation or action while being physically or figuratively positioned at the rear or out of direct view of another entity.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f08c2a4819093e772a1497c7ecc |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:32 p.m.