Triple
T6617886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hammer, hoe and brush emblem |
E149598
|
entity |
| Predicate | brushRepresents |
P71545
|
FINISHED |
| Object | intellectuals |
—
|
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: intellectuals | Statement: [hammer, hoe and brush emblem, brushRepresents, intellectuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brushRepresents Context triple: [hammer, hoe and brush emblem, brushRepresents, intellectuals]
-
A.
blueRepresents
Indicates that the color blue is used to symbolize, denote, or stand for a particular concept, state, or category in a given context.
-
B.
usesBrushworkType
Indicates that an entity employs or is characterized by a particular type or style of brushwork in its creation or execution.
-
C.
draws
Indicates that one entity creates a visual representation or image of another entity.
-
D.
rimRepresents
Indicates that one entity serves as a representation, model, or stand-in for another entity within a specific context or system.
-
E.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6bdb76ec48190b59d576170970cc9 |
completed | March 27, 2026, 5:26 p.m. |
Created at: March 27, 2026, 1:58 p.m.