Triple
T21488868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleo |
E530183
|
entity |
| Predicate | isWidely |
P139549
|
FINISHED |
| Object | performed |
—
|
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: performed | Statement: [Oleo, isWidely, performed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidely Context triple: [Oleo, isWidely, performed]
-
A.
isWidelyUsed
Indicates that something is commonly or extensively utilized across many contexts, users, or situations.
-
B.
isWidelyKnown
Indicates that something is generally recognized or familiar to a large number of people.
-
C.
isWidelyPerformed
chosen
Indicates that an action or behavior is carried out by a large number of individuals or groups across many contexts or locations.
-
D.
widerUsage
Indicates that one entity is used or applied more broadly, frequently, or in a greater variety of contexts than another.
-
E.
widelyCoveredBy
Indicates that something (such as an event, topic, or issue) receives extensive attention or reporting from many media outlets or information sources.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea390bd88190bc444e6af275f6e8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.