Triple
T37704979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudradaman I |
E939174
|
entity |
| Predicate | publicWork |
P30363
|
FINISHED |
| Object | repair of the Sudarshana lake dam |
—
|
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: repair of the Sudarshana lake dam | Statement: [Rudradaman I, publicWork, repair of the Sudarshana lake dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicWork Context triple: [Rudradaman I, publicWork, repair of the Sudarshana lake dam]
-
A.
otherWork
Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
-
B.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
C.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
D.
workOn
chosen
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
E.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: May 3, 2026, 4:18 p.m.