Triple
T26665998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellington Phoenix FC |
E672186
|
entity |
| Predicate | crossBorderClub |
P74114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wellington Phoenix FC, crossBorderClub, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderClub Context triple: [Wellington Phoenix FC, crossBorderClub, true]
-
A.
crossBorderCommunity
Indicates a relationship where a community spans or connects populations across one or more political or geographic borders.
-
B.
crossBorderPresence
Indicates that an entity maintains operations, activities, or influence that extend across national or jurisdictional borders.
-
C.
crossBorderRegion
Indicates a region that spans or intersects the boundary between two or more distinct territorial or jurisdictional areas.
-
D.
crossBorderTradeHub
Indicates a location or entity that serves as a central point for facilitating, coordinating, or processing trade activities that occur across national or regional borders.
-
E.
crossBorderLeague
chosen
Indicates that a sports league or competition includes teams or participants from multiple countries, crossing national borders.
- 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 3:09 a.m.