Triple
T3276582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diyarbakır |
E68771
|
entity |
| Predicate | cityWallsLength |
P33049
|
FINISHED |
| Object | approximately 5.5 km |
—
|
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: approximately 5.5 km | Statement: [Diyarbakır, cityWallsLength, approximately 5.5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWallsLength Context triple: [Diyarbakır, cityWallsLength, approximately 5.5 km]
-
A.
hasPeaceWalls
Indicates that there exist physical barriers or walls separating groups or areas to reduce or prevent conflict or violence between them.
-
B.
distanceFromHadriansWall
Indicates the measured spatial distance between a given entity and Hadrian’s Wall.
-
C.
hasBorderWallOrFence
Indicates that a physical barrier such as a wall or fence exists along the border between two entities.
-
D.
hasHistoricTownWallsRemnants
Indicates that remnants of historic town walls are present and associated with the subject entity.
-
E.
lengthInKm
chosen
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0128f08819084644f3c8fda2596 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.