Triple
T3662767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Marathon |
E77687
|
entity |
| Predicate | campaignObjectiveGreek |
P6636
|
FINISHED |
| Object | defense of Attica |
—
|
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: defense of Attica | Statement: [Battle of Marathon, campaignObjectiveGreek, defense of Attica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campaignObjectiveGreek Context triple: [Battle of Marathon, campaignObjectiveGreek, defense of Attica]
-
A.
campaignObjectiveContext
Indicates the specific situational or strategic context in which a campaign’s objective is defined or pursued.
-
B.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
C.
commercialObjective
Indicates that an action, plan, or entity is primarily intended to achieve commercial or business-related goals, such as generating revenue, profit, or market advantage.
-
D.
goals
chosen
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fcd910819082012b10b23860aa |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.