Triple
T28311473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glynco |
E714006
|
entity |
| Predicate | FLETCRole |
P164265
|
FINISHED |
| Object | site of FLETC headquarters |
—
|
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: site of FLETC headquarters | Statement: [Glynco, FLETCRole, site of FLETC headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FLETCRole Context triple: [Glynco, FLETCRole, site of FLETC headquarters]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
tacticalOfficer
Indicates that an entity serves in the role or capacity of a tactical officer in relation to another entity or organization.
-
C.
militaryBranchSupervised
Indicates that one military branch has authority over, or is responsible for overseeing and directing, another military branch.
-
D.
isMilitaryStaffOf
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
-
E.
mandatedRoleOfForce
Indicates that an authority has officially assigned or required a specific role or function for a particular force.
- F. None of above. chosen
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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e2e6608190957cfb801455930a |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 11:40 p.m.