Triple
T31033570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five-Day Battle in Lincoln |
E790794
|
entity |
| Predicate | centerOfFighting |
P39414
|
FINISHED |
| Object | McSween house in Lincoln |
—
|
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: McSween house in Lincoln | Statement: [Five-Day Battle in Lincoln, centerOfFighting, McSween house in Lincoln]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerOfFighting Context triple: [Five-Day Battle in Lincoln, centerOfFighting, McSween house in Lincoln]
-
A.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
B.
combat
Indicates that two or more entities are engaged in fighting or armed conflict with each other.
-
C.
primaryAxisOfCombat
Indicates the main direction or line along which opposing forces engage or conduct combat operations.
-
D.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of another entity.
-
E.
battlefieldOf
chosen
Indicates that a location is the site where a particular battle or military engagement 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694c3e0f881909ea3548ec8ab3eaf |
completed | May 3, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.