Triple
T26073014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dia!kwain |
E657600
|
entity |
| Predicate | dataTypeContributed |
P160328
|
FINISHED |
| Object | personal narratives |
—
|
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: personal narratives | Statement: [Dia!kwain, dataTypeContributed, personal narratives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeContributed Context triple: [Dia!kwain, dataTypeContributed, personal narratives]
-
A.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
D.
dataTypeSearched
Indicates that a particular data type is the target or focus of a search operation.
-
E.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
- F. None of above. chosen
Provenance (4 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606ccc3b8819082ca4366aaf48a70 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 7:31 p.m.