Triple
T21747350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAB Coronado |
E536821
|
entity |
| Predicate | hasTrainingAreaType |
P6822
|
FINISHED |
| Object | urban training facilities |
—
|
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: urban training facilities | Statement: [NAB Coronado, hasTrainingAreaType, urban training facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingAreaType Context triple: [NAB Coronado, hasTrainingAreaType, urban training facilities]
-
A.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
B.
hasAreaType
chosen
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
C.
hasStudyAreaType
Indicates that an entity’s study area is classified as a specific type or category (e.g., lab, field site, classroom).
-
D.
hasTrainingBaseIn
Indicates that an entity maintains or operates a training base located in a specified place.
-
E.
hasFieldTrainingComponent
Indicates that an entity includes or is associated with a component involving practical, in-the-field training activities.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a771b908190886cade242e263e4 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.