Triple
T35157333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germany B |
E1015158
|
entity |
| Predicate | nationalTeamCategory |
P99501
|
FINISHED |
| Object | secondary national team |
—
|
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: secondary national team | Statement: [Germany B, nationalTeamCategory, secondary national team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalTeamCategory Context triple: [Germany B, nationalTeamCategory, secondary national team]
-
A.
nationalTeamType
chosen
Indicates the specific category or level of a national team (e.g., senior, youth, futsal) with which an entity is associated.
-
B.
nationalTeamFor
Indicates that one entity serves as the national team representing another entity, typically a country or nation, in a given sport or activity.
-
C.
nationalTeamSport
Indicates that a particular sport is officially designated as the national team sport of a given country or region.
-
D.
nationalTeamSystem
Indicates a relationship where an entity is part of, governed by, or operates within a specific national team structure or organizational system.
-
E.
nationalTeamCode
Indicates the code that identifies the national team associated with an entity.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:02 p.m.