Triple
T18688426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland Tuatara |
E456926
|
entity |
| Predicate | crossBorderLeagueMember |
P74114
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Auckland Tuatara, crossBorderLeagueMember, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossBorderLeagueMember Context triple: [Auckland Tuatara, crossBorderLeagueMember, yes]
-
A.
crossBorderLeague
chosen
Indicates that a sports league or competition includes teams or participants from multiple countries, crossing national borders.
-
B.
crossBorderPartner
Indicates a partnership relationship between entities that operate across national or jurisdictional borders.
-
C.
crossBorderPeople
Indicates the movement or presence of people across national or regional borders.
-
D.
crossBorderPresence
Indicates that an entity maintains operations, activities, or influence that extend across national or jurisdictional borders.
-
E.
hasCrossBorderTies
Indicates that there exists a relationship or connection that extends across national or jurisdictional boundaries between the involved entities.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2e4c6081908bb958bd00d6bec9 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.