Triple
T28311474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glynco |
E714006
|
entity |
| Predicate | FLETCFunction |
P164265
|
FINISHED |
| Object | federal law enforcement training |
—
|
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: federal law enforcement training | Statement: [Glynco, FLETCFunction, federal law enforcement training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FLETCFunction Context triple: [Glynco, FLETCFunction, federal law enforcement training]
-
A.
FLETCRole
chosen
Indicates that an entity serves in a specific role or capacity within the FLETC (Federal Law Enforcement Training Centers) context.
-
B.
Petite ForceFunction
Indicates a functional relationship where a relatively small or delicate force is applied by one entity to influence or act upon another.
-
C.
functionInCitadel
Indicates that an entity serves a specific role or performs a particular function within a citadel.
-
D.
toolFunction
Indicates that one entity serves as a tool used to perform a particular function or achieve a specific purpose for another entity.
-
E.
tribalFunction
Indicates a role, duty, or activity that a tribe or tribal group performs or is responsible for.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:40 p.m.