Triple
T34664670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mooloos |
E890218
|
entity |
| Predicate | fanChantOrNicknameFor |
P49044
|
FINISHED |
| Object | Waikato supporters |
—
|
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: Waikato supporters | Statement: [Mooloos, fanChantOrNicknameFor, Waikato supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanChantOrNicknameFor Context triple: [Mooloos, fanChantOrNicknameFor, Waikato supporters]
-
A.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
B.
supporterGroupNickname
chosen
Indicates that a particular nickname is used to refer to a group of supporters associated with an entity.
-
C.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for another entity.
-
D.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
E.
fanChant
Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f574388190b75d8c00917bb6f5 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.