Triple
T30211424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan–Argive conflicts |
E768075
|
entity |
| Predicate | earliestDocumentedEvent |
P52040
|
FINISHED |
| Object | Battle of Hysiae (669 BC) |
—
|
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: Battle of Hysiae (669 BC) | Statement: [Spartan–Argive conflicts, earliestDocumentedEvent, Battle of Hysiae (669 BC)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestDocumentedEvent Context triple: [Spartan–Argive conflicts, earliestDocumentedEvent, Battle of Hysiae (669 BC)]
-
A.
earliestDocumentsDate
Indicates the earliest date on which the associated documents were created, recorded, or became valid.
-
B.
firstMajorEventAt
Indicates that the referenced event is the earliest major event associated with the given entity, specifying when that first significant occurrence takes place.
-
C.
earliestWellKnownExample
chosen
Indicates that one entity is the earliest well-known example or instance of the other entity.
-
D.
bestKnownEvent
Indicates that the referenced event is the most prominent, famous, or widely recognized event associated with the given entity.
-
E.
earliestDate
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 7:32 p.m.