Triple
T27976012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سرخپوشان |
E706491
|
entity |
| Predicate | جزء واژه «پوشان» |
P42778
|
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.
partlyCoveredBy
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
B.
مغطى_بـ
Indicates that one entity is covered by or has its surface overlaid with another entity.
-
C.
partOfLexicon
chosen
Indicates that a linguistic unit (such as a word or expression) belongs to or is included within a particular lexicon or vocabulary set.
-
D.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
E.
replacedPartOf
Indicates that one entity has taken the place of another entity as a component or part within a larger whole.
- 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_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:41 p.m.