Triple
T28583919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aero Glass |
E723441
|
entity |
| Predicate | successorFeature |
P149995
|
FINISHED |
| Object | Aero Lite theme |
—
|
NE NERFINISHED |
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: Aero Lite theme | Statement: [Aero Glass, successorFeature, Aero Lite theme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorFeature Context triple: [Aero Glass, successorFeature, Aero Lite theme]
-
A.
successorFeatureBasisFor
Indicates that one feature serves as the foundational basis or justification for the successor feature that follows it.
-
B.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
-
C.
successorFunctionally
chosen
Indicates that one entity functionally replaces or follows another in performing the same role, task, or purpose.
-
D.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
E.
successorType
Indicates the specific kind or category of successor relationship that holds between one entity and the next in a sequence or hierarchy.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 4:16 a.m.