Triple
T36572311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modular Equipment Transporter |
E902152
|
entity |
| Predicate | firstUseEvent |
P91680
|
FINISHED |
| Object | Apollo 14 first EVA on the Moon |
—
|
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: Apollo 14 first EVA on the Moon | Statement: [Modular Equipment Transporter, firstUseEvent, Apollo 14 first EVA on the Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseEvent Context triple: [Modular Equipment Transporter, firstUseEvent, Apollo 14 first EVA on the Moon]
-
A.
firstTimeEvent
Indicates that the referenced event is occurring for the first time and has not happened previously.
-
B.
firstUsedInEvent
chosen
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
-
C.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
D.
firstCreationAssociatedEvent
Indicates the event that is most closely associated with the initial creation of an entity.
-
E.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
- 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_69f76e6416708190a9754b8c52d4e453 |
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:11 p.m.