Triple
T22844475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poule d’Essai des Poulains |
E566175
|
entity |
| Predicate | historicalPrecursorStartYear |
P69538
|
FINISHED |
| Object | 1840 |
—
|
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: 1840 | Statement: [Poule d’Essai des Poulains, historicalPrecursorStartYear, 1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPrecursorStartYear Context triple: [Poule d’Essai des Poulains, historicalPrecursorStartYear, 1840]
-
A.
hasHistoricalOriginInYear
chosen
Indicates that something first originated, began, or came into existence in a specified calendar year.
-
B.
historicalPeriodOfFirstUse
Indicates the historical time period during which something was first used or came into use.
-
C.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
D.
historicallyFoundOn
Indicates that something was typically or commonly located on or associated with something else during a past historical period.
-
E.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
- 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_69e245869e188190a196584f36e682da |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8726d4819095b4d999b4172ff7 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:36 p.m.