Triple
T30162379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Ainos |
E766700
|
entity |
| Predicate | hasModernLocationName |
P43602
|
FINISHED |
| Object | Enez |
—
|
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: Enez | Statement: [Lords of Ainos, hasModernLocationName, Enez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernLocationName Context triple: [Lords of Ainos, hasModernLocationName, Enez]
-
A.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
B.
hasModernLocation
chosen
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
C.
hasModernLocationStatus
Indicates that an entity’s current or contemporary geographic location status is being specified or characterized.
-
D.
isModernName
Indicates that a given name is considered modern or contemporary in usage or origin, as opposed to traditional or historical.
-
E.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 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: April 29, 2026, 7:22 p.m.