Triple
T518782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roy Kirk |
E10766
|
entity |
| Predicate | inspiredEvent |
P15344
|
FINISHED |
| Object | Nomad's later merger with the alien probe Tan Ru |
—
|
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: Nomad's later merger with the alien probe Tan Ru | Statement: [Roy Kirk, inspiredEvent, Nomad's later merger with the alien probe Tan Ru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredEvent Context triple: [Roy Kirk, inspiredEvent, Nomad's later merger with the alien probe Tan Ru]
-
A.
portraysEvent
Indicates that one entity depicts, represents, or illustrates a particular event.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
annualEvent
Indicates that an event occurs once every year on a recurring basis.
-
D.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
E.
inspiredByPlace
Indicates that something (such as a work, idea, or creation) originates from or is significantly influenced by a particular location or environment.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f0151e8c81909a82b58ac0515eba |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f1137e948190838303cdaa757a5a |
completed | Feb. 28, 2026, 1:43 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.