Triple
T1480503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Whitecaps FC |
E30942
|
entity |
| Predicate | cityDerivation |
P29247
|
FINISHED |
| Object | named after earlier Vancouver Whitecaps teams |
—
|
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: named after earlier Vancouver Whitecaps teams | Statement: [Vancouver Whitecaps FC, cityDerivation, named after earlier Vancouver Whitecaps teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDerivation Context triple: [Vancouver Whitecaps FC, cityDerivation, named after earlier Vancouver Whitecaps teams]
-
A.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
B.
city1
Indicates that the subject is classified as a city.
-
C.
citySigned
Indicates that a city has formally signed or endorsed an agreement, document, or commitment.
-
D.
cityAssociatedWith
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
E.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c674cc9c819088fc9146c7a7a914 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c57984088190b2c2d2d9cc2e5df9 |
completed | March 1, 2026, 11:02 p.m. |
Created at: March 1, 2026, 8:11 p.m.