Triple
T20079318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Word |
E499955
|
entity |
| Predicate | isCreatorAgent |
P19389
|
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: [Eternal Word, isCreatorAgent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCreatorAgent Context triple: [Eternal Word, isCreatorAgent, true]
-
A.
hasCreatorRoleFor
Indicates that an entity serves in the role of creator for another entity, establishing a creator-to-created relationship.
-
B.
possibleCreator
Indicates that an entity is a plausible but not definitively confirmed creator or originator of another entity.
-
C.
hasAgent
chosen
Indicates that an action or event is carried out or initiated by a particular agent.
-
D.
isCustomOrFanCreated
Indicates that something has been created by fans or individuals outside the official or original source, rather than being an official or canonical work.
-
E.
hasWorkCreator
Indicates that an entity is the creator or originator of a particular work (such as a document, artwork, or other creative product).
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643f93208190ae2a413f88ea9aed |
completed | April 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.