Triple
T15154308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Gate (Split) |
E362029
|
entity |
| Predicate | hasCityWallFunction |
P117533
|
FINISHED |
| Object | defensive structure |
—
|
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: defensive structure | Statement: [Golden Gate (Split), hasCityWallFunction, defensive structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityWallFunction Context triple: [Golden Gate (Split), hasCityWallFunction, defensive structure]
-
A.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
B.
hasCityWallGates
Indicates that a city wall includes one or more gates that provide passage through it.
-
C.
isFortifiedCity
Indicates that a city is strengthened with defensive structures or fortifications, such as walls, ramparts, or similar protective works.
-
D.
followsOldCityWall
Indicates that something runs along or traces the path of an old city wall.
-
E.
hasWall
Indicates that one entity possesses, includes, or is bounded by a wall.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0060b0cd08190afad14cffcc7d93f |
completed | April 15, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:08 a.m.