Triple
T28996720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maclaurin buildings |
E736184
|
entity |
| Predicate | isIconicImageFor |
P160149
|
FINISHED |
| Object | MIT publicity materials |
—
|
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: MIT publicity materials | Statement: [Maclaurin buildings, isIconicImageFor, MIT publicity materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIconicImageFor Context triple: [Maclaurin buildings, isIconicImageFor, MIT publicity materials]
-
A.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
B.
isImageOf
chosen
Indicates that one entity is a visual depiction or representation of another entity.
-
C.
hasIconographicFigure
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
D.
isIconicAddressOf
Indicates that one entity is a widely recognized, emblematic, or culturally significant address associated with the other entity.
-
E.
hasIconicMask
Indicates that an entity is associated with or characterized by a distinctive, widely recognized mask.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fb6ef4881909a758c3538fdec03 |
completed | May 2, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:31 a.m.