Triple
T30463176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asha |
E775065
|
entity |
| Predicate | equivalentInNewPersian |
P67521
|
FINISHED |
| Object | Ardī |
—
|
NE NERFINISHED |
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: Ardī | Statement: [Asha, equivalentInNewPersian, Ardī]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equivalentInNewPersian Context triple: [Asha, equivalentInNewPersian, Ardī]
-
A.
hasMeaningInPersian
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Persian language.
-
B.
nameInNewPersian
chosen
Indicates that an entity’s name is expressed or recorded in the New Persian (modern Persian) language.
-
C.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
D.
languageEquivalent
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
-
E.
correspondsToInArabic
Indicates that one entity is the equivalent or matching counterpart of another entity specifically in the Arabic language.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:10 p.m.