Triple
T32666825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Este III |
E835176
|
entity |
| Predicate | chronologicallyBelongsTo |
P194086
|
FINISHED |
| Object | first millennium BC |
—
|
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 BC | Statement: [Este III, chronologicallyBelongsTo, first millennium BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallyBelongsTo Context triple: [Este III, chronologicallyBelongsTo, first millennium BC]
-
A.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
B.
chronologyPrecedes
Indicates that one event or state occurs earlier in time than another in a chronological sequence.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
E.
chronologicallyAmong
Indicates that one event or time point occurs within the temporal range defined by two other events or time points, preserving their chronological order.
- F. None of above. chosen
Provenance (4 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
| PDg | Predicate description generation | batch_69fd5f2903a48190ac4b718bff99c6cf |
completed | May 8, 2026, 3:57 a.m. |
Created at: May 1, 2026, 1:08 a.m.