Triple
T26712632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tower Forty-five |
E673460
|
entity |
| Predicate | cityWallType |
P161153
|
FINISHED |
| Object | medieval curtain wall tower |
—
|
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: medieval curtain wall tower | Statement: [Tower Forty-five, cityWallType, medieval curtain wall tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityWallType Context triple: [Tower Forty-five, cityWallType, medieval curtain wall tower]
-
A.
cityWallRelation
Indicates a structural or spatial relationship between a city and its surrounding wall, such as presence, connection, or association.
-
B.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
C.
cityWallLength
Indicates the measured length or extent of a city's defensive wall.
-
D.
hasCityWallFunction
Indicates that an entity serves the functional role of a city wall, such as providing defense, enclosure, or boundary protection for an urban area.
-
E.
builderOfCityWalls
Indicates that an entity is responsible for constructing or building the defensive walls of a city.
- F. None of above. chosen
Provenance (4 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617c196b48190bdd2734be9dbdc81 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:36 a.m.