Triple
T29518092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Guoan F.C. |
E748855
|
entity |
| Predicate | cityDerbyContext |
P93359
|
FINISHED |
| Object | Beijing |
—
|
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: Beijing | Statement: [Beijing Guoan F.C., cityDerbyContext, Beijing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDerbyContext Context triple: [Beijing Guoan F.C., cityDerbyContext, Beijing]
-
A.
cityDerby
Indicates a competitive or rivalry relationship between two cities, often in sports or similar local contests.
-
B.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
C.
cityDerbyName
Indicates that a city is known by a particular derby (rivalry match) name.
-
D.
isFromCityWithDerby
chosen
Indicates that an entity originates from a city that has a football (or sports) derby with another team from the same city.
-
E.
homeCityDerby
Indicates that two sports teams are based in the same city and their match-up constitutes a local rivalry or derby.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c65323c81909ea69757d4d77bd0 |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:38 p.m.