Triple
T4626793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carneia |
E101115
|
entity |
| Predicate | notableHistoricalConnection |
P16345
|
FINISHED |
| Object | Spartan delay at the Battle of Marathon |
—
|
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: Spartan delay at the Battle of Marathon | Statement: [Carneia, notableHistoricalConnection, Spartan delay at the Battle of Marathon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHistoricalConnection Context triple: [Carneia, notableHistoricalConnection, Spartan delay at the Battle of Marathon]
-
A.
historicalNotability
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
B.
historicalFigureAssociated
Indicates that there is a notable connection or linkage between an entity and a historical figure, such as influence, collaboration, representation, or involvement in the figure’s life or legacy.
-
C.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
-
D.
hasNotableHistoricalAssociation
Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
-
E.
historicallyLinked
chosen
Indicates that two entities are connected through a shared or related historical event, period, or development.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a0a7b588190bc6552ee5babb198 |
completed | March 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.