Triple
T27976004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سرخپوشان |
E706491
|
entity |
| Predicate | کاربرد |
P98
|
FINISHED |
| Object | اشاره به تیمهای ورزشی با رنگ قرمز |
—
|
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: اشاره به تیمهای ورزشی با رنگ قرمز | Statement: [سرخپوشان, کاربرد, اشاره به تیمهای ورزشی با رنگ قرمز]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: کاربرد Context triple: [سرخپوشان, کاربرد, اشاره به تیمهای ورزشی با رنگ قرمز]
-
A.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
appliedPrimarilyTo
Indicates that something is used mainly or chiefly in relation to a particular target, context, or purpose, rather than being used broadly or equally elsewhere.
-
D.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
E.
potentialUse
Indicates that one entity could be used for, or is suitable for, a particular function, purpose, or application involving 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 7:41 p.m.