Triple
T38061367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve of Destruction |
E950347
|
entity |
| Predicate | isMandatoryForCompletion |
P23639
|
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: [Eve of Destruction, isMandatoryForCompletion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMandatoryForCompletion Context triple: [Eve of Destruction, isMandatoryForCompletion, true]
-
A.
isMandatoryFor
chosen
Indicates that something is required or compulsory for another thing to occur, be valid, or be completed.
-
B.
isMandatoryIn
Indicates that the presence or inclusion of one entity is required or compulsory within the context, scope, or configuration of another entity.
-
C.
isObligatory
Indicates that an entity is required or must be performed, fulfilled, or complied with according to some rule, norm, or obligation.
-
D.
isCompleteFor
Indicates that one entity fully satisfies or finishes the requirements, scope, or intended purpose of another entity.
-
E.
isMandatoryInSomeJurisdictions
Indicates that the subject is legally required or compulsory in at least one jurisdiction or legal authority.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.