Triple
T6465027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeriba Shigan |
E142211
|
entity |
| Predicate | strandedOn |
P13798
|
FINISHED |
| Object | remote alien planet Fyrine IV (film setting) |
—
|
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: remote alien planet Fyrine IV (film setting) | Statement: [Jeriba Shigan, strandedOn, remote alien planet Fyrine IV (film setting)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strandedOn Context triple: [Jeriba Shigan, strandedOn, remote alien planet Fyrine IV (film setting)]
-
A.
shipwreckedOn
chosen
Indicates that an entity becomes stranded or marooned on a particular landmass or location as a result of a shipwreck.
-
B.
beachedAt
Indicates that something has come ashore and is stranded or resting on a beach at a particular location or time.
-
C.
isAbandonedAtSeaBy
Indicates that one entity is deliberately left behind or deserted at sea by another entity.
-
D.
madeLandfallOn
Indicates that a storm or similar weather system has come ashore and first reached land at a specific location or on a specific date.
-
E.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a10305081909521ee200cf70a30 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.