Triple
T34762747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunland |
E1002110
|
entity |
| Predicate | cultureOfInhabitantsRelatedTo |
P56388
|
FINISHED |
| Object | ancient Men of Eriador |
—
|
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: ancient Men of Eriador | Statement: [Dunland, cultureOfInhabitantsRelatedTo, ancient Men of Eriador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureOfInhabitantsRelatedTo Context triple: [Dunland, cultureOfInhabitantsRelatedTo, ancient Men of Eriador]
-
A.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
B.
fateOfInhabitants
Indicates the outcome or destiny that befalls the inhabitants of a place or group, such as survival, displacement, or death.
-
C.
inhabitedIn
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
D.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
E.
otherInhabitants
Indicates that there exist additional beings or residents associated with or present in the same place, group, or context as a referenced 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 3:59 p.m.