Triple
T25916620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande |
E653053
|
entity |
| Predicate | relatedWord |
P10003
|
FINISHED |
| Object | grand (English cognate) |
—
|
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: grand (English cognate) | Statement: [Grande, relatedWord, grand (English cognate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWord Context triple: [Grande, relatedWord, grand (English cognate)]
-
A.
linguisticallyRelatedTo
chosen
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
B.
relatedSpell
Indicates that there is an association or connection between two spells, such as similarity, dependency, or contextual relevance.
-
C.
closelyRelatedConcept
Indicates that two concepts share a strong, direct, and meaningful connection in meaning, function, or usage.
-
D.
relatedPaliName
Indicates that one entity has an associated or corresponding name expressed in Pali for the other entity.
-
E.
meaningIsRelatedTo
Indicates that one concept has a semantic or contextual connection to another concept without specifying the exact nature of that relationship.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 22, 2026, 8:31 a.m.