Triple
T26241798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torokina |
E656334
|
entity |
| Predicate | airfieldOperationalDuring |
P159633
|
FINISHED |
| Object | World War II |
—
|
NE NERFINISHED |
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: World War II | Statement: [Torokina, airfieldOperationalDuring, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airfieldOperationalDuring Context triple: [Torokina, airfieldOperationalDuring, World War II]
-
A.
airfieldOpened
Indicates that an airfield began operations or was officially opened at a certain time.
-
B.
airfieldUsedDuring
chosen
Indicates that an airfield was in operational use during a specified time period or event.
-
C.
operatedAirfields
Indicates that an entity had operational control over and actively used specific airfields.
-
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.
operatesAirport
Indicates that one entity manages and runs the operations of an airport.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60d8f7f9c8190bb8cb8f8ac4c0ca5 |
completed | May 2, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:03 p.m.