Triple
T4791690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibadat Khana |
E106615
|
entity |
| Predicate | languagesUsed |
P58450
|
FINISHED |
| Object | Persian |
—
|
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: Persian | Statement: [Ibadat Khana, languagesUsed, Persian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languagesUsed Context triple: [Ibadat Khana, languagesUsed, Persian]
-
A.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
B.
usedInProgrammingLanguages
Indicates that something (such as a concept, construct, or feature) is employed or implemented within one or more programming languages.
-
C.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
D.
usedByProgrammingLanguages
Indicates that something (such as a tool, library, paradigm, or feature) is employed or utilized by one or more programming languages.
-
E.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
- F. None of above. chosen
Provenance (4 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ddff388190b55071ed5cae7688 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:22 p.m.