Triple
T28801061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terje Hauge |
E727234
|
entity |
| Predicate | hasRefereedClubCompetitions |
P170392
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Terje Hauge, hasRefereedClubCompetitions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefereedClubCompetitions Context triple: [Terje Hauge, hasRefereedClubCompetitions, yes]
-
A.
hasOfficiatedClubs
chosen
Indicates that a person has served as an official (e.g., referee, umpire, or similar role) in matches involving the specified sports clubs.
-
B.
hadInternationalClubCompetition
Indicates that an entity has participated in or been involved with an international club-level competition.
-
C.
associatedClubUEFACompetition
Indicates that a club is linked to, or participates in, a specific UEFA-organized competition.
-
D.
hasPlayedWithClub
Indicates that an individual has been a member of and participated in activities or competitions for a particular club.
-
E.
refereedCompetition
Indicates that a competition is overseen by an official referee or judging authority who enforces rules and makes binding decisions.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: April 28, 2026, 6:27 a.m.