Triple
T37105616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 4872 |
E918831
|
entity |
| Predicate | selectedAsTargetFor |
P69992
|
FINISHED |
| Object | Cosmic Call 2003 |
—
|
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: Cosmic Call 2003 | Statement: [HIP 4872, selectedAsTargetFor, Cosmic Call 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedAsTargetFor Context triple: [HIP 4872, selectedAsTargetFor, Cosmic Call 2003]
-
A.
usesTargetsFrom
Indicates that one entity selects or operates on targets that are defined, provided, or referenced by another entity.
-
B.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
C.
aimedAtBy
chosen
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
-
D.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
E.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.