Triple
T31264519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oirats |
E797215
|
entity |
| Predicate | scriptInventedBy |
P632
|
FINISHED |
| Object | Zaya Pandita |
—
|
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: Zaya Pandita | Statement: [Oirats, scriptInventedBy, Zaya Pandita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptInventedBy Context triple: [Oirats, scriptInventedBy, Zaya Pandita]
-
A.
wasInventedBy
chosen
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
B.
hasInventorRoleOf
Indicates that an entity holds or fulfills the role of inventor with respect to another entity (such as an invention, patent, or creative work).
-
C.
notableInventor
Indicates that the subject is a well-known or historically significant inventor of the object.
-
D.
eponymousFounderOf
Indicates that a person is the namesake founder after whom an organization, place, or entity is named.
-
E.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 9:12 p.m.