Triple
T25270923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Big Bethel |
E633564
|
entity |
| Predicate | fortNearby |
P61270
|
FINISHED |
| Object | Fort Monroe |
E34064
|
NE 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: Fort Monroe | Statement: [Battle of Big Bethel, fortNearby, Fort Monroe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortNearby Context triple: [Battle of Big Bethel, fortNearby, Fort Monroe]
-
A.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
D.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
-
E.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
- F. None of above.
Provenance (4 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba1a1f88190b3db79ec06bfa994 |
completed | May 1, 2026, 11:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1067f85e4c8190865174db452467e0 |
completed | May 22, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:16 p.m.