Triple
T21900119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elnor |
E540784
|
entity |
| Predicate | orderDoctrine |
P4473
|
FINISHED |
| Object | only binds to lost causes |
—
|
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: only binds to lost causes | Statement: [Elnor, orderDoctrine, only binds to lost causes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderDoctrine Context triple: [Elnor, orderDoctrine, only binds to lost causes]
-
A.
acceptsDoctrine
Indicates that one entity acknowledges, adopts, or agrees to follow the doctrine put forward by another entity.
-
B.
usesDoctrine
chosen
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
C.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
D.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f11fca2bf88190b2a5b912aa102513 |
completed | April 28, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:07 p.m.