Triple
T34640371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvan Elvish |
E889538
|
entity |
| Predicate | usedByCharacterGroup |
P53533
|
FINISHED |
| Object | Wood-elves of Mirkwood |
—
|
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: Wood-elves of Mirkwood | Statement: [Silvan Elvish, usedByCharacterGroup, Wood-elves of Mirkwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByCharacterGroup Context triple: [Silvan Elvish, usedByCharacterGroup, Wood-elves of Mirkwood]
-
A.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
B.
usedByGroup
chosen
Indicates that something is utilized or employed by a particular group or collective entity.
-
C.
hasCharacterGroupName
Indicates that an entity is associated with a specific name identifying a group of characters.
-
D.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
E.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 2:04 a.m.