Triple
T28537811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2U |
E722212
|
entity |
| Predicate | airlineBaseMetropolitanArea |
P167365
|
FINISHED |
| Object | Tel Aviv metropolitan area |
—
|
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: Tel Aviv metropolitan area | Statement: [2U, airlineBaseMetropolitanArea, Tel Aviv metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineBaseMetropolitanArea Context triple: [2U, airlineBaseMetropolitanArea, Tel Aviv metropolitan area]
-
A.
airlineBaseCity
Indicates the city that serves as the primary operational base or headquarters location for an airline.
-
B.
associatedAirlineHeadquarters
Indicates that an airline is connected to or based at a particular headquarters location.
-
C.
associatedAirportFocusCityFor
Indicates that an airport serves as a designated focus city for a particular airline or carrier.
-
D.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
E.
airportLinkName
Indicates the name assigned to a transportation link or connection associated with an airport.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 3:33 a.m.