Triple
T7119620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianjin Jinmen Tiger F.C. |
E165913
|
entity |
| Predicate | tierInDomesticLeague |
P42313
|
FINISHED |
| Object | first tier |
—
|
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: first tier | Statement: [Tianjin Jinmen Tiger F.C., tierInDomesticLeague, first tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInDomesticLeague Context triple: [Tianjin Jinmen Tiger F.C., tierInDomesticLeague, first tier]
-
A.
tierInNationalFootball
Indicates the competitive level or division within a country's national football league system in which an entity (e.g., a club or team) participates.
-
B.
tierInLeagueSystem
chosen
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
C.
leagueType
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
D.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
E.
tierInDomesticSystem
Indicates the hierarchical level or rank that an entity occupies within a country's internal (domestic) system or structure.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e61b8a288190a165ea25adfaaef5 |
completed | March 27, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.