Triple
T130342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pequot War |
E2640
|
entity |
| Predicate | hasPrimaryTheater |
P687
|
FINISHED |
| Object | southeastern Connecticut |
—
|
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: southeastern Connecticut | Statement: [Pequot War, hasPrimaryTheater, southeastern Connecticut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryTheater Context triple: [Pequot War, hasPrimaryTheater, southeastern Connecticut]
-
A.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
B.
theaterOfWar
chosen
Indicates that a specified location or region is the primary area where a particular conflict, war, or military operation takes place.
-
C.
hasNumberOfTheatres
Indicates the quantity of theatres associated with or present in a given entity.
-
D.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
E.
theaterCommander
Indicates that an entity serves as the commanding authority over military operations within a specific theater or area of operations.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.