Triple
T30615213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemon Interrupt |
E779298
|
entity |
| Predicate | usedAsTransitionTo |
P3705
|
FINISHED |
| Object | progressive house |
—
|
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: progressive house | Statement: [Lemon Interrupt, usedAsTransitionTo, progressive house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsTransitionTo Context triple: [Lemon Interrupt, usedAsTransitionTo, progressive house]
-
A.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
B.
transitionedThrough
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
C.
usedToPrecede
Indicates that one entity regularly or habitually came before another in time or sequence in the past.
-
D.
supportsTransitionTo
Indicates that one state, condition, or entity enables or is compatible with moving or changing to another state, condition, or entity.
-
E.
transitionMechanismUsedWith
chosen
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
- F. None of above.
Provenance (3 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 8:26 p.m.