Triple
T7783608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howland Island |
E187185
|
entity |
| Predicate | runwayStatus |
P75082
|
FINISHED |
| Object | abandoned |
—
|
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: abandoned | Statement: [Howland Island, runwayStatus, abandoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayStatus Context triple: [Howland Island, runwayStatus, abandoned]
-
A.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
B.
runwayUsage
Indicates that a particular runway is being used or assigned for aircraft operations such as takeoffs or landings.
-
C.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
D.
runwaysUsableAt
Indicates that certain runways at a location are available and suitable for use (e.g., for takeoff or landing) at a given time or under specified conditions.
-
E.
runwayCharacteristic
chosen
Indicates a relationship where specific attributes or features are associated with a runway.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:22 p.m.