Triple
T25639032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herse |
E642784
|
entity |
| Predicate | temporaryDesignation |
P122119
|
FINISHED |
| Object | S/2003 J 17 |
—
|
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: S/2003 J 17 | Statement: [Herse, temporaryDesignation, S/2003 J 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryDesignation Context triple: [Herse, temporaryDesignation, S/2003 J 17]
-
A.
alternateDesignation
Indicates that one entity serves as an alternative name, label, or identifier for another entity.
-
B.
isTemporaryDesignation
Indicates that a given designation or label is intended to be used only for a limited time and is not the entity’s permanent or final designation.
-
C.
initiallyDesignated
Indicates that an entity was assigned or specified in a particular role, state, or configuration at the beginning of a process or time period.
-
D.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
-
E.
temporaryNameOf
chosen
Indicates that one entity serves as a provisional or interim name assigned to another entity, intended to be replaced by a permanent name later.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa64332081909df65f8b4380f152 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 5:38 p.m.