Triple
T30600637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvish languages |
E778893
|
entity |
| Predicate | hasFictionalSpeaker |
P196082
|
FINISHED |
| Object | Elves |
—
|
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: Elves | Statement: [Elvish languages, hasFictionalSpeaker, Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalSpeaker Context triple: [Elvish languages, hasFictionalSpeaker, Elves]
-
A.
hasFictionalSpokesperson
Indicates that an entity is represented or promoted by a spokesperson who is a fictional or imaginary character.
-
B.
hasFictionalPerformer
Indicates that an entity is associated with a performer who is a fictional or imaginary character rather than a real person.
-
C.
hasFictionalAddressee
Indicates that an entity (such as a text or communication) is directed toward or addressed to an addressee that is fictional rather than a real person or audience.
-
D.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
-
E.
hasFictionalRole
Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
- F. None of above. chosen
Provenance (4 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 29, 2026, 8:25 p.m.