Triple
T34040720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 vs. 100 (UK) |
E872934
|
entity |
| Predicate | numberOfOpponents |
P148920
|
FINISHED |
| Object | 100 mob members |
—
|
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: 100 mob members | Statement: [1 vs. 100 (UK), numberOfOpponents, 100 mob members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfOpponents Context triple: [1 vs. 100 (UK), numberOfOpponents, 100 mob members]
-
A.
opponentsCount
chosen
Indicates the number of distinct opposing entities involved in a given context or interaction.
-
B.
numberOfOpponentsBeaten
Indicates the count of distinct opponents that an entity has successfully defeated.
-
C.
hasDistanceBetweenOpponents
Indicates that there is a measurable spatial separation between two opposing entities.
-
D.
opponentStrength
Indicates the level or degree of power, skill, or capability possessed by an opposing party in a competitive or adversarial context.
-
E.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.