Triple
T10678967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naïve art |
E251692
|
entity |
| Predicate | gainedRecognition |
P95265
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Naïve art, gainedRecognition, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedRecognition Context triple: [Naïve art, gainedRecognition, late 19th century]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
C.
wasRecognizedAs
Indicates that an entity was formally identified, acknowledged, or designated as having a particular role, status, or quality.
-
D.
seeksRecognitionOf
Indicates that one entity actively pursues acknowledgment, validation, or formal recognition from another entity.
-
E.
notableAwardRecognition
Indicates that an entity has received or been formally recognized with a notable award or honor.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb9684e48190b2786823723cde6c |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:10 p.m.