Triple
T3134264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fayetteville, North Carolina |
E65489
|
entity |
| Predicate | hasMajorMilitaryPresence |
P14275
|
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: [Fayetteville, North Carolina, hasMajorMilitaryPresence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorMilitaryPresence Context triple: [Fayetteville, North Carolina, hasMajorMilitaryPresence, true]
-
A.
hasMilitaryPresence
chosen
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
B.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
C.
hasPeacekeepingForcesFrom
Indicates that an entity hosts or is supported by peacekeeping forces that originate from another specified entity.
-
D.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
E.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada562540081908627950dd0b56a1e |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df840088190a26a1516f4c1f056 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.