Triple
T26200332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harappan religion |
E655211
|
entity |
| Predicate | knowledgeBasis |
P157114
|
FINISHED |
| Object | iconographic interpretation |
—
|
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: iconographic interpretation | Statement: [Harappan religion, knowledgeBasis, iconographic interpretation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knowledgeBasis Context triple: [Harappan religion, knowledgeBasis, iconographic interpretation]
-
A.
knowledgeType
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
-
B.
knowledgeScope
Indicates the extent or range of information, topics, or understanding that an entity possesses or is concerned with.
-
C.
knowledgeSource
chosen
Indicates that one entity serves as the origin, provider, or reference of information or understanding for another entity.
-
D.
knowledgeOutput
Indicates that an entity produces, expresses, or makes available knowledge, information, or learned content as an output.
-
E.
knowledgeForm
Indicates the specific format, structure, or representation in which knowledge is expressed or encoded within a system or context.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdaeebc81909c7587f038ad6246 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:48 p.m.