Triple
T747486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseverance rover |
E15374
|
entity |
| Predicate | nameSelectedBy |
P381
|
FINISHED |
| Object | student naming contest |
—
|
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: student naming contest | Statement: [Perseverance rover, nameSelectedBy, student naming contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameSelectedBy Context triple: [Perseverance rover, nameSelectedBy, student naming contest]
-
A.
nameChosenToBe
Indicates that an entity has been given or selected to have a particular name.
-
B.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
-
C.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
D.
nameOf
Indicates that one entity is the name or designation of another entity.
-
E.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a62dd1bc819094a3814654448ae3 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ff10608190bfd60b4a1cb38f7d |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.