Triple
T23904079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln (surname) |
E601136
|
entity |
| Predicate | isToponymicFrom |
P97773
|
FINISHED |
| Object | the city of Lincoln in England |
—
|
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: the city of Lincoln in England | Statement: [Lincoln (surname), isToponymicFrom, the city of Lincoln in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isToponymicFrom Context triple: [Lincoln (surname), isToponymicFrom, the city of Lincoln in England]
-
A.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
B.
hasOriginToponym
chosen
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
C.
hasToponymicAssociation
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
D.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
-
E.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde0674c8190a5e1ce0315ae83cd |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.