Triple
T6471685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Airport |
E142366
|
entity |
| Predicate | hasFireCategory |
P60199
|
FINISHED |
| Object | Category 3 (variable by operation) |
—
|
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: Category 3 (variable by operation) | Statement: [Cambridge Airport, hasFireCategory, Category 3 (variable by operation)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireCategory Context triple: [Cambridge Airport, hasFireCategory, Category 3 (variable by operation)]
-
A.
hasFireEvent
Indicates that a fire-related incident or occurrence is associated with, or has taken place involving, a given entity.
-
B.
fireType
chosen
Indicates that one entity has a specific classification or category related to fire (e.g., type, kind, or nature of fire).
-
C.
hasFireHistory
Indicates that an entity has experienced one or more fire events in the past.
-
D.
notableFire
Indicates that a significant or historically important fire event is associated with the subject.
-
E.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a2fd4248190a789bf0301e2860a |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:50 p.m.