Triple
T6070023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall of Maastricht |
E135256
|
entity |
| Predicate | hasCentralAxis |
P68472
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [City Hall of Maastricht, hasCentralAxis, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralAxis Context triple: [City Hall of Maastricht, hasCentralAxis, yes]
-
A.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
B.
hasCentralSection
Indicates that an entity possesses a distinct middle or central part within its overall structure or composition.
-
C.
hasCentralFigure
Indicates that something features a primary or most important figure at its core or focus.
-
D.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
E.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
- 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05742867481908e3f45c875807c73 |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8d4a148190bd8f95caae978e1b |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:10 p.m.