Triple
T35777102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puerta del Cambrón |
E1034326
|
entity |
| Predicate | hasCityGateType |
P188475
|
FINISHED |
| Object | double-arched gate |
—
|
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: double-arched gate | Statement: [Puerta del Cambrón, hasCityGateType, double-arched gate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityGateType Context triple: [Puerta del Cambrón, hasCityGateType, double-arched gate]
-
A.
hasCityGateFunction
Indicates that something serves the role or function of a city gate, such as controlling access, passage, or boundary between a city and its surroundings.
-
B.
hasCityGateStatus
Indicates the status or condition of a city gate in relation to a given entity.
-
C.
hasCityGateRemains
Indicates that a location contains surviving structural remains of a former city gate.
-
D.
hasGatewayCity
Indicates that one place serves as the primary gateway city (main entry or transit hub) for accessing another place.
-
E.
hasGateNumber
Indicates that an entity (such as a flight or departure) is associated with a specific gate number.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba789c1188190973a919bfe2871f3 |
completed | May 6, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:06 p.m.