Triple
T17407939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fair Oaks Station |
E423268
|
entity |
| Predicate | dateOfAssociatedBattle |
P19740
|
FINISHED |
| Object | 1862-05-31 |
—
|
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: 1862-05-31 | Statement: [Fair Oaks Station, dateOfAssociatedBattle, 1862-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfAssociatedBattle Context triple: [Fair Oaks Station, dateOfAssociatedBattle, 1862-05-31]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
associatedWithBattle
Indicates a relationship where an entity is connected or linked to a specific battle, such as by participation, relevance, or involvement.
-
C.
battleDateRelation
chosen
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
-
D.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
E.
yearOfBattle
Indicates the specific calendar year in which a particular battle took 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b08d5a881909e7a5b2ae2c60898 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.