Triple
T38583169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Iron dwarves |
E932289
|
entity |
| Predicate | sharesCouncilWith |
P202920
|
FINISHED |
| Object | Bronzebeard dwarves |
—
|
NE NERFINISHED |
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: Bronzebeard dwarves | Statement: [Dark Iron dwarves, sharesCouncilWith, Bronzebeard dwarves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCouncilWith Context triple: [Dark Iron dwarves, sharesCouncilWith, Bronzebeard dwarves]
-
A.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
B.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
C.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
D.
sharesQuestWith
Indicates that two or more entities are participating in, or have access to, the same quest or mission.
-
E.
sharesIn
Indicates that one entity holds or possesses shares or ownership stakes in another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00d08e8fac8190b59359134e6e1c03 |
completed | May 10, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_6a00d0127c088190a6f5b360450af113 |
completed | May 10, 2026, 6:36 p.m. |
| PDg | Predicate description generation | batch_6a00d08de20881908d83d98362e0751c |
completed | May 10, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.