Triple
T36717680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbarians vs New Zealand 1973 |
E906957
|
entity |
| Predicate | BarbariansCaptain |
P186189
|
FINISHED |
| Object | Phil Bennett |
—
|
NE NERFINISHED |
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: Phil Bennett | Statement: [Barbarians vs New Zealand 1973, BarbariansCaptain, Phil Bennett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BarbariansCaptain Context triple: [Barbarians vs New Zealand 1973, BarbariansCaptain, Phil Bennett]
-
A.
VandalCommander
Indicates a relationship where one entity serves as the commander or leader of a group of vandals.
-
B.
GallicCommander
Indicates a person who holds a commanding or leadership role over Gallic forces or within a Gallic context.
-
C.
ParthianCommander
Indicates that an entity serves as a military commander within the Parthian context or forces.
-
D.
NumidianCommander
Indicates that an entity serves as a military commander associated with Numidia or Numidian forces.
-
E.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force 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_69f7c841388481909a408b704b30f9c7 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.