Triple
T33620867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men of Arnor |
E861263
|
entity |
| Predicate | continentInFictional |
P90336
|
FINISHED |
| Object | Middle-earth |
—
|
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: Middle-earth | Statement: [Men of Arnor, continentInFictional, Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continentInFictional Context triple: [Men of Arnor, continentInFictional, Middle-earth]
-
A.
belongsToFictionalContinent
chosen
Indicates that something is located on, associated with, or a part of a specific fictional continent within an imagined world.
-
B.
fictionalGeographicRegion
Indicates that a geographic region exists only in fiction or imagination rather than in the real world.
-
C.
fictionalSettingRegion
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
D.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
E.
continentType
Indicates that one entity is classified as a specific type or category of continent in relation to 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:41 a.m.