Triple
T28436705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran Aseman Airlines Flight 3704 |
E715285
|
entity |
| Predicate | flightPathRegion |
P51005
|
FINISHED |
| Object | southwestern Iran |
—
|
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: southwestern Iran | Statement: [Iran Aseman Airlines Flight 3704, flightPathRegion, southwestern Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightPathRegion Context triple: [Iran Aseman Airlines Flight 3704, flightPathRegion, southwestern Iran]
-
A.
routeRegion
chosen
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
B.
flightRoute
Indicates a path or sequence of locations that a particular flight travels between, typically from its origin to its destination (and possibly via intermediate stops).
-
C.
languageRegionsAlongRoute
Indicates the languages spoken in the geographic regions that lie along a specified route.
-
D.
trackRegion
Indicates that an entity is associated with, occurs within, or is relevant to a specific geographic or logical region used for tracking.
-
E.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e3a2c18819085f3e19fa534da4c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:43 a.m.