Triple
T950662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H. A. Maaskant |
E20512
|
entity |
| Predicate | architecturalTypeSpecialty |
P4631
|
FINISHED |
| Object | large-scale buildings |
—
|
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: large-scale buildings | Statement: [H. A. Maaskant, architecturalTypeSpecialty, large-scale buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecturalTypeSpecialty Context triple: [H. A. Maaskant, architecturalTypeSpecialty, large-scale buildings]
-
A.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
B.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
-
D.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
E.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d62e408190855b2883407f6c6b |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.