Triple
T5876323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-IVB |
E130633
|
entity |
| Predicate | expendedAs |
P67375
|
FINISHED |
| Object | impactor on the Moon in some missions |
—
|
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: impactor on the Moon in some missions | Statement: [S-IVB, expendedAs, impactor on the Moon in some missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expendedAs Context triple: [S-IVB, expendedAs, impactor on the Moon in some missions]
-
A.
expenditures
Indicates that an entity spends or allocates money or resources, typically specifying the amount, purpose, or category of that spending.
-
B.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
-
C.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
D.
dissipatedIn
Indicates that something (such as energy, heat, or a substance) is lost, spread out, or converted within a particular medium, location, or system.
-
E.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0432f06fc8190bc047d52ffc30d59 |
completed | March 22, 2026, 7:29 p.m. |
Created at: March 22, 2026, 3:57 p.m.