Triple
T27976010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سرخپوشان |
E706491
|
entity |
| Predicate | ریشهٔ واژه |
P5801
|
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.
etymologicalRootMeaning
Indicates that one term’s meaning originates from or is derived from the historical or original meaning of another term.
-
B.
etymologicalRootName
Indicates that one name is derived from, or originates etymologically in, another name.
-
C.
etymologicalSource
chosen
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
D.
etymologicalField
Indicates that one term belongs to a particular semantic or conceptual domain relevant to its etymological origin or historical development.
-
E.
etymology
Indicates the historical origin and development of a word or term, including its source language and form.
- 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_69f63b38a5c081908edb1c9a415c914b |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:41 p.m.