Triple
T37661660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | usedForAdvancement |
P98
|
FINISHED |
| Object | Eye Spy |
—
|
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: Eye Spy | Statement: [Eye of Ender, usedForAdvancement, Eye Spy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForAdvancement Context triple: [Eye of Ender, usedForAdvancement, Eye Spy]
-
A.
typeOfAdvance
Indicates that one entity represents a specific kind or category of advance (e.g., payment, progress, or development) in relation to another entity.
-
B.
advancementControl
Indicates a relationship where one entity directs, manages, or regulates the progress or forward movement of another entity or process.
-
C.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
advancementStatus
Indicates the current stage or progress state of an ongoing process, project, or development.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 3, 2026, 4:18 p.m.