Triple
T35065959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonesy |
E1011729
|
entity |
| Predicate | staysBehindWhile |
P162181
|
FINISHED |
| Object | Ellen Ripley travels to LV-426 in Aliens |
—
|
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: Ellen Ripley travels to LV-426 in Aliens | Statement: [Jonesy, staysBehindWhile, Ellen Ripley travels to LV-426 in Aliens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: staysBehindWhile Context triple: [Jonesy, staysBehindWhile, Ellen Ripley travels to LV-426 in Aliens]
-
A.
isBehind
Indicates that one entity is positioned to the rear of another entity along a relevant spatial or directional axis.
-
B.
staysWith
Indicates that one entity remains in the company or presence of another entity for a period of time.
-
C.
locatedBehind
Indicates that one entity is positioned at the rear of or on the far side of another entity along a given viewing or reference direction.
-
D.
leftBehind
chosen
Indicates that one entity remains in a place or situation after another entity has departed or moved on.
-
E.
keepsAt
Indicates that an entity stores or maintains another entity at a specific location or position.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78613f9dc8190b20a15c22090d27f |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.