Triple
T37551482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Violet Hold |
E933599
|
entity |
| Predicate | encounterStructure |
P190544
|
FINISHED |
| Object | wave-based event |
—
|
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: wave-based event | Statement: [The Violet Hold, encounterStructure, wave-based event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterStructure Context triple: [The Violet Hold, encounterStructure, wave-based event]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
associatesStructure
Indicates a relationship where one entity is linked or connected to a particular structure, typically to denote that the structure is relevant, attached, or functionally associated with it.
-
C.
commonStructure
Indicates that two or more entities share the same or a very similar internal organization, pattern, or arrangement.
-
D.
regionStructureDiscussed
Indicates that a particular anatomical or spatial region is the main subject of discussion or analysis in a given context.
-
E.
subjectStructure
Indicates that one entity serves as the structural form, framework, or configuration in which the other entity is organized or embodied.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.