Triple
T24377849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nursina |
E614526
|
entity |
| Predicate | modernEquivalentPlace |
P155515
|
FINISHED |
| Object | Norcia |
—
|
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: Norcia | Statement: [Nursina, modernEquivalentPlace, Norcia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernEquivalentPlace Context triple: [Nursina, modernEquivalentPlace, Norcia]
-
A.
modernEquivalent
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
-
B.
modernLocationOfCity
chosen
Indicates that a historical or former city is located within the boundaries of a specified modern administrative or geographic entity.
-
C.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
-
D.
modernNameOfServedSettlement
Indicates that the object is the current, modern name of the settlement that is or was served by the subject (e.g., a facility, infrastructure, or service).
-
E.
historicalLocationNowIn
Indicates that an entity’s historical location is now situated within the boundaries of another, current geographic or political 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293d96e7c8190b2f33a8fd12c32c6 |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.