Triple
T25667847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/2017 J 2 |
E643572
|
entity |
| Predicate | isUnresolvedInDetail |
P123042
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [S/2017 J 2, isUnresolvedInDetail, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnresolvedInDetail Context triple: [S/2017 J 2, isUnresolvedInDetail, true]
-
A.
notResolvedBy
Indicates that an issue, problem, or request remains unresolved despite the involvement or actions of a specified entity.
-
B.
hasUnresolvedHistoricalDetails
chosen
Indicates that certain aspects of the relationship or event remain historically unclear, incomplete, or not fully verified.
-
C.
isEarlyResolutionIn
Indicates that one event, action, or process constitutes an earlier or preliminary resolution within the context of another, broader resolution or case.
-
D.
resolvedIn
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
-
E.
hasResolution
Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to another entity.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3096ec8190bebd54d74fa8e1ba |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:08 p.m.