Triple
T18785301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium |
E459356
|
entity |
| Predicate | hasOrdinalForm |
P4901
|
FINISHED |
| Object | first millennium |
—
|
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: first millennium | Statement: [Millennium, hasOrdinalForm, first millennium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinalForm Context triple: [Millennium, hasOrdinalForm, first millennium]
-
A.
hasOrdinalSeries
Indicates that one entity belongs to, or is positioned within, an ordered sequence or series relative to other entities.
-
B.
ordinalNumber
chosen
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
C.
usedOrdinal
Indicates that one entity is used as an ordinal indicator or position marker relative to another entity.
-
D.
hasNotableBearerOrdinalNumber
Indicates that an entity is associated with a notable bearer identified by a specific ordinal position (e.g., first, second, third) among others with the same name or title.
-
E.
hasNumeral
Indicates that one entity is associated with a numeral representation or numeric symbol of another 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978154ac819096356d2a488b45f0 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.