Triple
T11860995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virūḍhaka |
E282155
|
entity |
| Predicate | guardianshipScope |
P79851
|
FINISHED |
| Object | southern quarter of the world |
—
|
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: southern quarter of the world | Statement: [Virūḍhaka, guardianshipScope, southern quarter of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianshipScope Context triple: [Virūḍhaka, guardianshipScope, southern quarter of the world]
-
A.
guardianInstitution
Indicates that an institution serves as a guardian or protective authority responsible for the care, oversight, or safeguarding of another entity.
-
B.
scopeOfControl
chosen
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
C.
hasGuardianCommunity
Indicates that an entity is under the protection, oversight, or care of a specific guardian community.
-
D.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
E.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.