Triple
T1250922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telugu script |
E26871
|
entity |
| Predicate | sisterScript |
P25820
|
FINISHED |
| Object | Kannada script |
—
|
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: Kannada script | Statement: [Telugu script, sisterScript, Kannada script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterScript Context triple: [Telugu script, sisterScript, Kannada script]
-
A.
sisterBase
Indicates that one entity is the sister of another, sharing at least one parent and being female relative to the other entity.
-
B.
sisterService
Indicates a relationship where two services are related as counterparts or peers, typically offered by the same provider or within the same system, without one being subordinate to the other.
-
C.
sisterInstallation
Indicates that two installations are related as counterparts or peers, typically within the same organization or system, without one being subordinate to the other.
-
D.
sisterChannel
Indicates that one channel is a sibling or counterpart to another channel, typically under the same ownership or network.
-
E.
sibling
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf84c73c8190bbb14265cd7ab6ae |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc49693c8190978ec63a5171d342 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:47 p.m.