Triple
T6984499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League B |
E161928
|
entity |
| Predicate | teamStrength |
P74296
|
FINISHED |
| Object | mid-ranked European national 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: mid-ranked European national teams | Statement: [League B, teamStrength, mid-ranked European national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamStrength Context triple: [League B, teamStrength, mid-ranked European national teams]
-
A.
opponentStrength
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
-
B.
teamScoring
Indicates that a team achieves a score or points in a game, match, or competitive event.
-
C.
teamBase
Indicates that one entity serves as the primary or foundational team associated with another entity.
-
D.
teamBuilt
Indicates that one entity created, assembled, or established a team that includes or is composed of another entity.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dbbc00fc8190a18221524b774021 |
completed | March 27, 2026, 7:34 p.m. |
Created at: March 27, 2026, 2:31 p.m.