Triple
T29544006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohirric |
E749580
|
entity |
| Predicate | relatedInFictionTo |
P106091
|
FINISHED |
| Object | Westron |
—
|
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: Westron | Statement: [Rohirric, relatedInFictionTo, Westron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedInFictionTo Context triple: [Rohirric, relatedInFictionTo, Westron]
-
A.
relatedToInFiction
chosen
Indicates that one entity is connected to another within a fictional context, such as a story, universe, or narrative work.
-
B.
worksWithInFiction
Indicates that two fictional characters are depicted as collaborating, interacting, or being associated with each other within a narrative work.
-
C.
associatedWithCaseInFiction
Indicates that an entity is connected to, involved in, or relevant to a particular case or investigation within a fictional context.
-
D.
associatedPeriodInFiction
Indicates a relationship where a fictional work, character, or event is linked to a specific time period within its fictional universe or narrative setting.
-
E.
createsInFiction
Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: April 28, 2026, 5:05 p.m.