Triple
T28743844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C4F |
E731312
|
entity |
| Predicate | garrisonNearCity |
P19869
|
FINISHED |
| Object | Jacksonville, Florida |
—
|
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: Jacksonville, Florida | Statement: [C4F, garrisonNearCity, Jacksonville, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonNearCity Context triple: [C4F, garrisonNearCity, Jacksonville, Florida]
-
A.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
-
B.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
-
C.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
D.
garrisonOrAssemblyArea
chosen
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
E.
garrisonDuringWar
Indicates that a military force is stationed in a specific location for defense or control during a time of war.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:04 a.m.