Triple
T33371802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super League 2 Greece |
E854509
|
entity |
| Predicate | topFlightBelow |
P176556
|
FINISHED |
| Object | Super League Greece |
—
|
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: Super League Greece | Statement: [Super League 2 Greece, topFlightBelow, Super League Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topFlightBelow Context triple: [Super League 2 Greece, topFlightBelow, Super League Greece]
-
A.
topFlightAbove
Indicates that one flight path or aircraft is positioned vertically higher than another in a given airspace or reference frame.
-
B.
topFlightRelationship
Indicates a relationship where one entity is the primary or most important flight associated with another entity, such as a top-ranked, preferred, or main flight option.
-
C.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
D.
topFlightStatus
Indicates the current operational or service status assigned to a flight within a top-level or primary flight schedule.
-
E.
positionRelativeToTopFlight
Indicates the relative vertical placement of something with respect to the topmost flight (e.g., of stairs or levels).
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:35 a.m.