Triple
T33113080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sindarin |
E847379
|
entity |
| Predicate | termInUniverse |
P47705
|
FINISHED |
| Object | Sindarin dialect of the North |
—
|
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: Sindarin dialect of the North | Statement: [North Sindarin, termInUniverse, Sindarin dialect of the North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termInUniverse Context triple: [North Sindarin, termInUniverse, Sindarin dialect of the North]
-
A.
hasInUniverseRole
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
B.
inUniverseStar
Indicates that a star exists or is located within a particular fictional or defined universe.
-
C.
inUniverse
chosen
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
D.
eraInUniverse
Indicates the specific time period or era during which something exists or occurs within a particular fictional or defined universe.
-
E.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:27 a.m.