Triple
T34574634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Period V |
E887716
|
entity |
| Predicate | usedInChronologySystem |
P187396
|
FINISHED |
| Object | Montelius system |
—
|
NE NERFINISHED |
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: Montelius system | Statement: [Period V, usedInChronologySystem, Montelius system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChronologySystem Context triple: [Period V, usedInChronologySystem, Montelius system]
-
A.
usedInCalendarSystem
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
B.
usedForChronology
chosen
Indicates that something is employed to establish, organize, or reference the order and timing of events.
-
C.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
D.
usedForCivilTimeIn
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
-
E.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 1, 2026, 2:03 a.m.