Triple
T4593643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barra Airport beach runway |
E103556
|
entity |
| Predicate | usesSurface |
P58186
|
FINISHED |
| Object | sand |
—
|
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: sand | Statement: [Barra Airport beach runway, usesSurface, sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSurface Context triple: [Barra Airport beach runway, usesSurface, sand]
-
A.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
B.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
-
C.
hasPrimarySurface
Indicates that one entity serves as the main or principal surface associated with another entity.
-
D.
formerSurface
Indicates that one entity previously served as the surface or outer layer of another entity, but no longer does so.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd593cf8508190acfc6ddb5716e80a |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.