Triple
T12233440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Front |
E291532
|
entity |
| Predicate | isArchitecturallyProminent |
P10074
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [South Front, isArchitecturallyProminent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArchitecturallyProminent Context triple: [South Front, isArchitecturallyProminent, true]
-
A.
hasArchitecturalSignificance
chosen
Indicates that something possesses notable architectural qualities, importance, or influence that make it worthy of special attention or recognition.
-
B.
heritageDesignation
Indicates that an entity has been formally assigned a specific cultural, historical, or heritage protection status by an authority.
-
C.
hasHeritageDesignation
Indicates that an entity has been formally assigned a specific heritage or cultural protection status by an authoritative body.
-
D.
hasHeritageListedPlace
Indicates that an entity possesses or is associated with a place that is officially designated as heritage-listed.
-
E.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.