Triple
T4007874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fawley |
E89569
|
entity |
| Predicate | hasNearbyHistoricUse |
P51359
|
FINISHED |
| Object | military aviation at Calshot |
—
|
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: military aviation at Calshot | Statement: [Fawley, hasNearbyHistoricUse, military aviation at Calshot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricUse Context triple: [Fawley, hasNearbyHistoricUse, military aviation at Calshot]
-
A.
hasFormerUseNearby
chosen
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
-
B.
hasNearbyHistoricPeriod
Indicates that one historic period occurs close in time or space to another historic period.
-
C.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
D.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.