Triple
T5663655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albanopolis |
E124803
|
entity |
| Predicate | locationCertainty |
P34406
|
FINISHED |
| Object | uncertain |
—
|
LITERAL FINISHED |
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: uncertain | Statement: [Albanopolis, locationCertainty, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationCertainty Context triple: [Albanopolis, locationCertainty, uncertain]
-
A.
locationSignedNear
Indicates that an entity’s location is in close physical proximity to another specified place or reference point.
-
B.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
C.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
D.
locationStatus
chosen
Indicates the current state or condition of an entity with respect to a specific location (e.g., present, absent, en route, or unknown).
-
E.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.