Triple
T6262192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Academy Dundigal |
E140325
|
entity |
| Predicate | hasSimulators |
P31906
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Air Force Academy Dundigal, hasSimulators, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimulators Context triple: [Air Force Academy Dundigal, hasSimulators, yes]
-
A.
hasSimulator
chosen
Indicates that one entity provides or is associated with a simulator used to model, emulate, or test the behavior of another entity.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
hasNumberOfPlatforms
Indicates the relationship that specifies how many platforms are associated with a given entity.
-
D.
hasSoftwareCompatibilityWith
Indicates that one software system can operate correctly and effectively with another software system, without conflicts or required modifications.
-
E.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06386a7b48190b032edd12078c5bc |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.