Triple
T29661904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Monumental |
E750431
|
entity |
| Predicate | frequentUseBy |
P157033
|
FINISHED |
| Object | CONMEBOL for major matches |
—
|
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: CONMEBOL for major matches | Statement: [El Monumental, frequentUseBy, CONMEBOL for major matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentUseBy Context triple: [El Monumental, frequentUseBy, CONMEBOL for major matches]
-
A.
frequentlyUsedBy
chosen
Indicates that something is regularly or commonly utilized by a particular entity.
-
B.
frequentUseCase
Indicates a situation, scenario, or pattern of use that occurs regularly or more often than others in relation to the subject.
-
C.
frequentlyVisitedBy
Indicates that an entity is regularly or often visited by another entity.
-
D.
isMoreFrequentlyUsedThan
Indicates that one entity is used or occurs with greater frequency than another entity.
-
E.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 28, 2026, 6:59 p.m.