Triple
T30361161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Promise box set |
E772289
|
entity |
| Predicate | containsArchivalMaterial |
P198573
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Promise box set, containsArchivalMaterial, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsArchivalMaterial Context triple: [The Promise box set, containsArchivalMaterial, true]
-
A.
usesArchivalMaterial
Indicates that one entity makes use of archival materials (such as historical records, documents, or collections) in relation to another entity or activity.
-
B.
hasArchaeologicalMaterial
Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
-
C.
hasArchitecturalMaterial
Indicates that something is constructed from, incorporates, or is characterized by a particular architectural material.
-
D.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
E.
archivesHeldIn
Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69fef3cdea708190af41c1ff23b68f88 |
completed | May 9, 2026, 8:43 a.m. |
Created at: April 29, 2026, 7:58 p.m.