Triple
T31814105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porte Saint-Jean |
E812086
|
entity |
| Predicate | hasCityWallRole |
P180986
|
FINISHED |
| Object | western gate of Old Quebec |
—
|
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: western gate of Old Quebec | Statement: [Porte Saint-Jean, hasCityWallRole, western gate of Old Quebec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCityWallRole Context triple: [Porte Saint-Jean, hasCityWallRole, western gate of Old Quebec]
-
A.
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.
-
B.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
C.
hasCityWallsFrom
Indicates that a city’s defensive walls originate from, or were constructed starting at, a specified source location or structure.
-
D.
hasCityWallOrientation
Indicates the directional orientation or alignment of a city’s defensive wall relative to cardinal or geographic directions.
-
E.
hasCityWallGates
Indicates that a city wall includes one or more gates that provide passage through it.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 30, 2026, 11:44 p.m.