Triple
T3279912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Lamartine |
E68846
|
entity |
| Predicate | hasTimePeriodOfNotability |
P8452
|
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: [Place Lamartine, hasTimePeriodOfNotability, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimePeriodOfNotability Context triple: [Place Lamartine, hasTimePeriodOfNotability, late 19th century]
-
A.
notableDuring
chosen
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
B.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
timePeriodOfNotableBearer
Indicates the span of time during which a notable bearer is recognized as having held, embodied, or been associated with the subject.
-
E.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0166c8c81909cb0a580ef319be3 |
completed | March 8, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.