Triple
T22490938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Even Pellerud |
E556013
|
entity |
| Predicate | hasWorkedAtLevel |
P86605
|
FINISHED |
| Object | international football |
—
|
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: international football | Statement: [Even Pellerud, hasWorkedAtLevel, international football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkedAtLevel Context triple: [Even Pellerud, hasWorkedAtLevel, international football]
-
A.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
B.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
hasWorkingLevel
Indicates that one entity possesses or is assigned a specific operational or functional level within a defined system or context.
-
D.
worksAtLevel
chosen
Indicates that an entity performs work or holds a role at a specified hierarchical or organizational level.
-
E.
hasExperienceOf
Indicates that one entity has undergone, encountered, or lived through a particular event, situation, or activity associated with another entity.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c40930c81908310ac6afd98c62e |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.