Triple
T38602088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackburn B-20 |
E934241
|
entity |
| Predicate | landingMedium |
P191281
|
FINISHED |
| Object | water |
—
|
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: water | Statement: [Blackburn B-20, landingMedium, water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingMedium Context triple: [Blackburn B-20, landingMedium, water]
-
A.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
B.
landingConfiguration
Indicates the specific arrangement or setup used for an entity’s landing phase or landing operation.
-
C.
landingSiteAttempt
Indicates an attempt by an entity to use or reach a particular location as a landing site, regardless of whether the landing ultimately succeeds.
-
D.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
E.
majorTrafficSource
Indicates that one entity serves as the primary or most significant source of traffic (e.g., visitors, data, or network requests) for another entity.
- F. None of above. chosen
Provenance (4 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.