Triple
T32696497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marsi |
E836021
|
entity |
| Predicate | eventStartBefore |
P42309
|
FINISHED |
| Object | Social War (91–88 BCE) |
—
|
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: Social War (91–88 BCE) | Statement: [Marsi, eventStartBefore, Social War (91–88 BCE)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventStartBefore Context triple: [Marsi, eventStartBefore, Social War (91–88 BCE)]
-
A.
eventBefore
chosen
Indicates that one event occurs earlier in time than another event.
-
B.
meetsBefore
Indicates that one entity encounters or meets another at some point in time that occurs earlier than a specified reference meeting or event.
-
C.
eventInConflict
Indicates that an event occurs within, is part of, or is directly associated with a specific conflict.
-
D.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
E.
timeSpanEndsBefore
Indicates that one time span concludes entirely before the starting point of another time span, with no overlap between them.
- 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:10 a.m.