Triple
T3336275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes' Square |
E70146
|
entity |
| Predicate | hasCentralColumn |
P13119
|
FINISHED |
| Object | column with Archangel Gabriel statue |
—
|
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: column with Archangel Gabriel statue | Statement: [Heroes' Square, hasCentralColumn, column with Archangel Gabriel statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralColumn Context triple: [Heroes' Square, hasCentralColumn, column with Archangel Gabriel statue]
-
A.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
B.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
C.
hasFrontColumns
Indicates that one entity possesses or features columns located at its front side.
-
D.
hasColumns
chosen
Indicates that one entity possesses or is characterized by a set of columns associated with it.
-
E.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bad97481909359e914d44a1a74 |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.