Triple
T4513860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surya |
E102109
|
entity |
| Predicate | lokaAssociation |
P21614
|
FINISHED |
| Object | rules Surya-loka |
—
|
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: rules Surya-loka | Statement: [Surya, lokaAssociation, rules Surya-loka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lokaAssociation Context triple: [Surya, lokaAssociation, rules Surya-loka]
-
A.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
-
B.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
hasTerritorialAssociation
chosen
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
E.
placeOfAssociation
Indicates a relationship where an entity is connected or affiliated with a specific place, such as where it is based, active, or commonly associated.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572402f481908151f7899bc96306 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.