Triple
T2507661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA World Cup Trophy |
E52621
|
entity |
| Predicate | usedInEventFrequency |
P29070
|
FINISHED |
| Object | every four years |
—
|
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: every four years | Statement: [FIFA World Cup Trophy, usedInEventFrequency, every four years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEventFrequency Context triple: [FIFA World Cup Trophy, usedInEventFrequency, every four years]
-
A.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
B.
hasEventFrequency
chosen
Indicates how often a particular event occurs within a given time period.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd65d6a988190aaaac8e98540a14f |
completed | March 7, 2026, 7:40 a.m. |
| PD | Predicate disambiguation | batch_69abd0bd996c8190ba8b9d6e4333b8d4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.