Triple
T27976021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سرخپوشان |
E706491
|
entity |
| Predicate | نوع نامگذاری |
P44079
|
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.
تصنيف النوع
Indicates the classification relationship that assigns an entity to a particular type or category.
-
B.
nomenclaturalTypeGenus
Indicates that one genus serves as the nomenclatural (name-bearing) type for a higher-ranked taxon, anchoring the application and definition of that taxon's name.
-
C.
namingBasis
chosen
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
-
D.
namedAfterTypeGenus
Indicates that an entity (such as a taxonomic group) is named after its type genus.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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.