Triple
T9771069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Navy bases in Florida |
E237124
|
entity |
| Predicate | hasPrimaryFunctions |
P88
|
FINISHED |
| Object | aviation 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: aviation training | Statement: [United States Navy bases in Florida, hasPrimaryFunctions, aviation training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFunctions Context triple: [United States Navy bases in Florida, hasPrimaryFunctions, aviation training]
-
A.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
C.
hasPrimaryActivities
Indicates that an entity is associated with one or more main activities that define its core functions or operations.
-
D.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
-
E.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f329148190a5e531478bc18073 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.