Triple
T36790663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rock of Chickamauga |
E909043
|
entity |
| Predicate | earnedDuring |
P4341
|
FINISHED |
| Object | Battle of Chickamauga |
—
|
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 Chickamauga | Statement: [The Rock of Chickamauga, earnedDuring, Battle of Chickamauga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earnedDuring Context triple: [The Rock of Chickamauga, earnedDuring, Battle of Chickamauga]
-
A.
earnedCurrency
Indicates that an entity has obtained a specified amount or type of currency as a result of some activity, work, or transaction.
-
B.
ownedDuring
Indicates that one entity possessed or held ownership of another entity for some or all of a specified time interval.
-
C.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
D.
spentEntireCareerWith
Indicates that an individual has worked exclusively for a single organization or team for the full duration of their professional career.
-
E.
usedDuring
chosen
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca93bd0481909d6eee9e950001a1 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.