Triple
T36717586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbarian F.C. |
E906955
|
entity |
| Predicate | traditionalOpponents |
P200634
|
FINISHED |
| Object | 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: national teams | Statement: [Barbarian F.C., traditionalOpponents, national teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalOpponents Context triple: [Barbarian F.C., traditionalOpponents, national teams]
-
A.
traditionalOppositionSeries
Indicates a relationship where entities are arranged as contrasting or opposing elements within a conventional or historically established sequence or set.
-
B.
regularOpponent
Indicates that two entities frequently compete against each other as recurring opponents in some contest or competitive context.
-
C.
opponentSupporters
Indicates that the related entities are supporters or backers of opposing sides in a contest, conflict, or competition.
-
D.
consideredOpponentsAs
Indicates that one entity regarded or treated another entity as an opponent or adversary.
-
E.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69ff9bec9d748190869caebf6bf0c78f |
completed | May 9, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:12 p.m.