Triple
T12777437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Kirwan |
E305413
|
entity |
| Predicate | wasKeyMemberOf |
P44793
|
FINISHED |
| Object | dominant All Blacks teams of the late 1980s |
—
|
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: dominant All Blacks teams of the late 1980s | Statement: [John Kirwan, wasKeyMemberOf, dominant All Blacks teams of the late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyMemberOf Context triple: [John Kirwan, wasKeyMemberOf, dominant All Blacks teams of the late 1980s]
-
A.
hasMemberWhoBecame
Indicates that a group or organization includes at least one member who later attained or transitioned into a specified role, status, or affiliation.
-
B.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
C.
keyMember
chosen
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
D.
hadMember
Indicates that an entity was formerly a member or part of another entity or group.
-
E.
hasFormerStaffMember
Indicates that an entity once had a person as a staff member, but that person is no longer employed there.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e595e008190b42dff3012d17d66 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.