Triple
T28312248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Rationalism |
E714028
|
entity |
| Predicate | notableArchitectGroup |
P202814
|
FINISHED |
| Object | Gruppo 7 |
—
|
NE NERFINISHED |
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: Gruppo 7 | Statement: [Italian Rationalism, notableArchitectGroup, Gruppo 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArchitectGroup Context triple: [Italian Rationalism, notableArchitectGroup, Gruppo 7]
-
A.
architectNotedFor
Indicates that an architect is recognized or distinguished for a particular work, style, contribution, or achievement.
-
B.
architectIsNotableFor
Indicates that an architect is recognized or distinguished for a particular work, contribution, or achievement.
-
C.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
D.
majorFigureInArchitecture
Indicates that an entity is recognized as a leading or highly influential figure within the field of architecture.
-
E.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
| PDg | Predicate description generation | batch_6a00bf5899b08190ad012a0879907d65 |
completed | May 10, 2026, 5:24 p.m. |
Created at: April 27, 2026, 11:41 p.m.