Triple
T10476599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adikavi |
E247058
|
entity |
| Predicate | adiMeans |
P637
|
FINISHED |
| Object | first |
—
|
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: first | Statement: [Adikavi, adiMeans, first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adiMeans Context triple: [Adikavi, adiMeans, first]
-
A.
aka
Indicates that one entity is also known by an alternative name or alias that refers to the same thing.
-
B.
aria
Indicates that an entity is associated with ARIA (Accessible Rich Internet Applications) attributes or roles that define how it should be interpreted by assistive technologies.
-
C.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
D.
is
chosen
Indicates that two entities are equivalent, share an attribute, or stand in a specified state or relation to each other.
-
E.
isADROf
Indicates a relationship where one entity serves as the Authorized Designated Responsible Officer (ADRO) for another entity, typically bearing formal oversight or accountability on its behalf.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095021e081908dfaa467938c13fd |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:21 p.m.