Triple
T27798912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ApplicationMaster |
E702186
|
entity |
| Predicate | lifecycleEndsWhen |
P94367
|
FINISHED |
| Object | application finishes or fails |
—
|
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: application finishes or fails | Statement: [ApplicationMaster, lifecycleEndsWhen, application finishes or fails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleEndsWhen Context triple: [ApplicationMaster, lifecycleEndsWhen, application finishes or fails]
-
A.
lifecycleEnd
Indicates that an entity has reached the conclusion of its existence, validity, or operational period.
-
B.
lifecycleStartsWhen
Indicates that the lifecycle of one entity begins at the time or event defined by another entity.
-
C.
lifecycleTiedTo
chosen
Indicates that the existence, duration, or validity of one entity is dependent on and ends with the lifecycle of another entity.
-
D.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
E.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 5:33 p.m.