Triple
T34883290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineering and Manufacturing Development phase |
E1006069
|
entity |
| Predicate | exitDecision |
P65611
|
FINISHED |
| Object | Milestone C |
—
|
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: Milestone C | Statement: [Engineering and Manufacturing Development phase, exitDecision, Milestone C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitDecision Context triple: [Engineering and Manufacturing Development phase, exitDecision, Milestone C]
-
A.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
B.
decisionToWithdraw
Indicates that an entity has made a choice or resolution to pull back from, discontinue, or remove involvement in something.
-
C.
closureDecision
Indicates a decision has been made to permanently or temporarily close an entity, operation, or process.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decisionOutput
chosen
Indicates that a decision-making process produces or yields a particular outcome or result.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.