Triple
T35397780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemisium |
E1023128
|
entity |
| Predicate | timeOfMajorEvent |
P105686
|
FINISHED |
| Object | 480 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: 480 BC | Statement: [Artemisium, timeOfMajorEvent, 480 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfMajorEvent Context triple: [Artemisium, timeOfMajorEvent, 480 BC]
-
A.
notableEventTime
chosen
Indicates the specific time at which a notable or significant event occurred.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
D.
chronologicallyNotableEvent
Indicates that an event is significant or noteworthy in terms of its position or impact within a chronological sequence of events.
-
E.
firstMajorEventAt
Indicates that the referenced event is the earliest major event associated with the given entity, specifying when that first significant occurrence takes place.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:03 p.m.