Triple
T6070010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Hall of Maastricht |
E135256
|
entity |
| Predicate | hasFacadeOrder |
P1109
|
FINISHED |
| Object | pilasters |
—
|
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: pilasters | Statement: [City Hall of Maastricht, hasFacadeOrder, pilasters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFacadeOrder Context triple: [City Hall of Maastricht, hasFacadeOrder, pilasters]
-
A.
hasOrder
chosen
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasSVOOrder
Indicates that a language or construction follows a basic word order where the subject comes first, followed by the verb, and then the object.
-
C.
hasFacet
Indicates that an entity possesses a particular aspect, side, or dimension as one of its distinguishable parts or characteristics.
-
D.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
-
E.
hasTraditionalOrderFollowedBy
Indicates that one item directly succeeds another according to an established or customary ordering.
- 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_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. |
Created at: March 22, 2026, 4:10 p.m.