Triple
T7355129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passenger 57 |
E169602
|
entity |
| Predicate | featuresHijacking |
P33464
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Passenger 57, featuresHijacking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresHijacking Context triple: [Passenger 57, featuresHijacking, true]
-
A.
hijacked
chosen
Indicates that one entity has forcibly taken control of another entity, typically without authorization and against the will of its rightful controller.
-
B.
featuresInversion
Indicates that one entity exhibits or incorporates an inversion of another entity, such as a reversed, mirrored, or otherwise inverted form or structure.
-
C.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
D.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
-
E.
featuresCross
Indicates that one feature or element intersects or passes across another in space or structure.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.