Triple
T32666774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Este I |
E835174
|
entity |
| Predicate | usedChronologicallyBy |
P104021
|
FINISHED |
| Object | Italian protohistoric archaeology |
—
|
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: Italian protohistoric archaeology | Statement: [Este I, usedChronologicallyBy, Italian protohistoric archaeology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedChronologicallyBy Context triple: [Este I, usedChronologicallyBy, Italian protohistoric archaeology]
-
A.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
B.
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.
-
C.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
D.
chronologyUsedBy
chosen
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
E.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7a9734c81909c42ab13b7b33001 |
completed | May 3, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:08 a.m.