Triple
T18174566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETI Artist in Residence program |
E435122
|
entity |
| Predicate | pairs |
P74541
|
FINISHED |
| Object | artists |
—
|
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: artists | Statement: [SETI Artist in Residence program, pairs, artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairs Context triple: [SETI Artist in Residence program, pairs, artists]
-
A.
pairBond
Indicates a long-term, typically exclusive social or reproductive partnership formed between two individuals.
-
B.
starPairing
Indicates a relationship where two stars are associated or grouped together as a pair, typically for observational, analytical, or classificatory purposes.
-
C.
pairedSingleWith
chosen
Indicates that one entity is matched or associated as a single counterpart with another single entity, typically forming an exclusive one-to-one pairing.
-
D.
commonPair
Indicates that two entities commonly occur together or are frequently associated as a pair in some shared context.
-
E.
matches
Indicates that two entities correspond to or are in agreement with each other according to some defined criteria or pattern.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df5900788190994525954a89fa3c |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.