Triple
T29760890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadley’s Hope |
E753763
|
entity |
| Predicate | firstContactWithXenomorphs |
P203183
|
FINISHED |
| Object | Russ Jorden’s expedition |
—
|
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: Russ Jorden’s expedition | Statement: [Hadley’s Hope, firstContactWithXenomorphs, Russ Jorden’s expedition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstContactWithXenomorphs Context triple: [Hadley’s Hope, firstContactWithXenomorphs, Russ Jorden’s expedition]
-
A.
firstRecontactWithEarth
Indicates the event or point in time when contact is re-established with Earth for the first time after a period of no communication.
-
B.
firstContactWithHumans
Indicates that the subject entity is the first to establish contact or interaction with humans.
-
C.
firstSolarEncounter
Indicates the initial interaction or contact an entity has with a solar system, star, or solar environment for the first time.
-
D.
firstContactContext
Indicates the circumstances or situation under which two entities first came into contact or interacted.
-
E.
firstRendezvousMission
Indicates that the mission is the first instance in which two or more entities conduct a rendezvous operation.
- F. None of above. chosen
Provenance (4 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a0136e4af808190b529d324bbf0c5d9 |
completed | May 11, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_6a01369141c4819091cb8064913a44ca |
completed | May 11, 2026, 1:53 a.m. |
| PDg | Predicate description generation | batch_6a0136e3d6ec8190898b5ab5a628a99d |
completed | May 11, 2026, 1:54 a.m. |
Created at: April 28, 2026, 8:33 p.m.