Triple
T8097138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian Super Cup |
E189012
|
entity |
| Predicate | hasResultType |
P2702
|
FINISHED |
| Object | one-leg final only |
—
|
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: one-leg final only | Statement: [Iranian Super Cup, hasResultType, one-leg final only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResultType Context triple: [Iranian Super Cup, hasResultType, one-leg final only]
-
A.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
B.
resultType
chosen
Indicates the type or category of outcome that is produced by a given process, action, or operation.
-
C.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
D.
hasFlowType
Indicates the type or category of flow associated with or exhibited by an entity.
-
E.
hasRootType
Indicates that an entity possesses or is associated with a primary or fundamental type that serves as its root classification.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb429319048190b612c8060a9a24d2 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:30 p.m.