Triple
T2917093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Venturi |
E78631
|
entity |
| Predicate | hasPartInHisWork |
P7332
|
FINISHED |
| Object | concept of "Less is a bore" |
—
|
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: concept of "Less is a bore" | Statement: [Robert Venturi, hasPartInHisWork, concept of "Less is a bore"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInHisWork Context triple: [Robert Venturi, hasPartInHisWork, concept of "Less is a bore"]
-
A.
hasPartInHisDesign
Indicates that one entity is included as a component or element within the design or plan created by another entity.
-
B.
hasFatherNotableWork
Indicates that a person's father is associated with a specific notable work or achievement.
-
C.
hasPartInBiography
Indicates that a person or entity is featured or plays a role within someone’s biographical account.
-
D.
notableWorkContained
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
-
E.
partOfAuthorBibliography
chosen
Indicates that a work is included in the set of publications that make up an author's bibliography.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:53 p.m.