Triple
T8258287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya |
E193124
|
entity |
| Predicate | hasMeaningInSanskrit |
P81241
|
FINISHED |
| Object | illusion |
—
|
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: illusion | Statement: [Maya, hasMeaningInSanskrit, illusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeaningInSanskrit Context triple: [Maya, hasMeaningInSanskrit, illusion]
-
A.
hasMeaningInPersian
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning when interpreted in the Persian language.
-
B.
hasMeaningViaJohn
Indicates that something possesses or conveys its meaning specifically through John as the interpretive or mediating agent.
-
C.
hasMeaningInKhmer
Indicates that something (such as a word, phrase, or symbol) possesses a specific meaning or interpretation in the Khmer language.
-
D.
stringMeaning
Indicates that one entity represents the semantic content or interpretation of a given string associated with another entity.
-
E.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fce9308190ac36512e80b06b52 |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb44d1caa881909069fa925a91316b |
completed | March 31, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:49 p.m.