Triple
T35976530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mainbreak |
E1040433
|
entity |
| Predicate | hasWaveShape |
P188922
|
FINISHED |
| Object | powerful walls |
—
|
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: powerful walls | Statement: [Mainbreak, hasWaveShape, powerful walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaveShape Context triple: [Mainbreak, hasWaveShape, powerful walls]
-
A.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
B.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
hasBellShape
Indicates that something possesses a form or outline resembling a bell.
-
D.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
E.
hasWaveConsistency
Indicates that the related entities maintain a stable, coherent pattern or behavior across successive waves, phases, or iterations.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbaf18085481908c774e8f8bbb9a41 |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbaebbb7f88190b4edfd9b83550aad |
completed | May 6, 2026, 9:12 p.m. |
Created at: May 3, 2026, 4:07 p.m.