Triple
T3326594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Horse I |
E69929
|
entity |
| Predicate | significantPeriodInArtistCareer |
P25964
|
FINISHED |
| Object | early 1910s |
—
|
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: early 1910s | Statement: [Blue Horse I, significantPeriodInArtistCareer, early 1910s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantPeriodInArtistCareer Context triple: [Blue Horse I, significantPeriodInArtistCareer, early 1910s]
-
A.
significantFigureInArtistLife
Indicates that one entity played an important or influential role in the life or career of the artist entity.
-
B.
timeInArtistCareer
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
C.
notableEventInCareer
Indicates that a particular event is a significant or defining occurrence within an entity’s professional career.
-
D.
notableWorkPeriod
chosen
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
E.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
- 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_69ad85a1829881908942c14075644d0d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb16dc170819086a63e033e17d8b3 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.