Triple
T36437287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Chaplin Hills |
E897620
|
entity |
| Predicate | isMajorEngagement |
P195837
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Chaplin Hills, isMajorEngagement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorEngagement Context triple: [Battle of Chaplin Hills, isMajorEngagement, true]
-
A.
isMajorEngagementIn
Indicates that an event or action constitutes a primary or significant engagement occurring within a specified context, setting, or larger operation.
-
B.
isMinorEngagement
Indicates that the engagement or interaction between entities is of low significance, scale, or impact compared to major engagements.
-
C.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
D.
isMajorEvent
chosen
Indicates that an event is of significant importance, scale, or impact compared to typical or minor events.
-
E.
isMajorHit
Indicates that something (such as a work, product, or performance) has achieved a high level of success, popularity, or impact.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:10 p.m.