Triple
T37661649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | canBeUsedInEnd |
P138698
|
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: [Eye of Ender, canBeUsedInEnd, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedInEnd Context triple: [Eye of Ender, canBeUsedInEnd, true]
-
A.
canEndOn
Indicates that one entity is allowed or able to terminate, conclude, or finish with another specified entity or condition.
-
B.
canBeUsed
chosen
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
C.
appliesToEndUse
Indicates that something (such as a rule, measure, or specification) is relevant or applicable to a particular end use or final application.
-
D.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
E.
canBeConcludedWith
Indicates that one situation, process, or sequence is able to be finished, resolved, or brought to an end by another specified action or condition.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.