Triple
T33432074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noldolantë (fragmentary) |
E856155
|
entity |
| Predicate | fictionalRaceConcerned |
P51003
|
FINISHED |
| Object | Noldor |
—
|
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: Noldor | Statement: [Noldolantë (fragmentary), fictionalRaceConcerned, Noldor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalRaceConcerned Context triple: [Noldolantë (fragmentary), fictionalRaceConcerned, Noldor]
-
A.
fictionalEthnicFocus
Indicates that something is primarily concerned with, centered on, or thematically emphasizes a fictional or invented ethnic group.
-
B.
relatedRace
chosen
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
C.
fictionalEthnoCulturalIdentity
Indicates that an entity is associated with an invented or imaginary ethnic or cultural identity, rather than a real-world one.
-
D.
hasEthnicityInFiction
Indicates that a fictional character or entity is portrayed as having a particular ethnicity within a narrative or fictional context.
-
E.
fictionalSpecies
Indicates that the subject is a species that exists only in fiction or imaginary works, rather than in real life.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:36 a.m.