Triple
T847487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn Aura |
E18307
|
entity |
| Predicate | hybridSystem |
P840
|
FINISHED |
| Object | mild hybrid system (Green Line) |
—
|
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: mild hybrid system (Green Line) | Statement: [Saturn Aura, hybridSystem, mild hybrid system (Green Line)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hybridSystem Context triple: [Saturn Aura, hybridSystem, mild hybrid system (Green Line)]
-
A.
partOfSystem
chosen
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
B.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
C.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
D.
oneOfThreeMajorSystems
Indicates that the subject is one of three primary or principal systems within a defined group or context.
-
E.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac0ba6b4819089c15ed7e1765502 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.