Triple
T27098892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harshavardhana |
E686384
|
entity |
| Predicate | sourceDescribedBy |
P163471
|
FINISHED |
| Object | Bana |
—
|
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: Bana | Statement: [Harshavardhana, sourceDescribedBy, Bana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceDescribedBy Context triple: [Harshavardhana, sourceDescribedBy, Bana]
-
A.
sourceDescribedBy
chosen
Indicates that a source is documented, characterized, or otherwise explained by a particular description or descriptive resource.
-
B.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
C.
source
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
D.
describedByURL
Indicates that an entity is documented, explained, or otherwise described at the given URL.
-
E.
describedFrom
Indicates that something is characterized, explained, or defined based on information, perspective, or features originating from a particular source or reference point.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:46 a.m.