Triple
T7309373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indus seals |
E168051
|
entity |
| Predicate | researchIssue |
P24329
|
FINISHED |
| Object | undeciphered writing system |
—
|
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: undeciphered writing system | Statement: [Indus seals, researchIssue, undeciphered writing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchIssue Context triple: [Indus seals, researchIssue, undeciphered writing system]
-
A.
researchTopic
chosen
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
B.
researchPriority
Indicates that one entity is designated as a subject or area of research that should receive prioritized attention or resources relative to others.
-
C.
researchOutcome
Indicates that an action, study, or investigation produces a specific result, finding, or conclusion.
-
D.
researchContribution
Indicates that an entity has produced or participated in creating new knowledge, findings, or innovations within a research context.
-
E.
researchModel
Indicates that an entity systematically investigates, develops, or analyzes a model as part of a research process.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebdbd6f481908e69e53dab452656 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.