Triple
T15193929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes and Villains |
E363095
|
entity |
| Predicate | hasModularRecordingApproach |
P117076
|
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: [Heroes and Villains, hasModularRecordingApproach, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModularRecordingApproach Context triple: [Heroes and Villains, hasModularRecordingApproach, true]
-
A.
isModular
Indicates that something is composed of distinct, interchangeable parts or units that can be independently created, modified, or replaced within a larger whole.
-
B.
recordingMethod
Indicates the technique or process used to capture or record something (such as data, audio, or video).
-
C.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
D.
recordingMode
Indicates the method or configuration by which something is recorded, such as how data, audio, or video capture is performed.
-
E.
hasRecordingContract
Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067eb710819085211fd05d5fa5f0 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:10 a.m.