Triple
T19113835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forney Army Airfield |
E467855
|
entity |
| Predicate | runwayMarkings |
P15986
|
FINISHED |
| Object | military standard |
—
|
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 standard | Statement: [Forney Army Airfield, runwayMarkings, military standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayMarkings Context triple: [Forney Army Airfield, runwayMarkings, military standard]
-
A.
hasRunwayMarkings
chosen
Indicates that a runway possesses specific painted markings or symbols on its surface.
-
B.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
-
C.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
D.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
-
E.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.