Triple
T27327717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Island |
E689702
|
entity |
| Predicate | runwaysStatus |
P170646
|
FINISHED |
| Object | disused |
—
|
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: disused | Statement: [Eastern Island, runwaysStatus, disused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwaysStatus Context triple: [Eastern Island, runwaysStatus, disused]
-
A.
runwayPresence
Indicates the existence or availability of a runway at or associated with the referenced location or facility.
-
B.
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.
-
C.
runwayInformationAvailableIn
Indicates that information about a runway is available within or through a specified medium, source, or context.
-
D.
runwayUsage
Indicates that a particular runway is being used or assigned for aircraft operations such as takeoffs or landings.
-
E.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 11:36 a.m.