Triple
T36254261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Themis (disputed Jovian moon) |
E891888
|
entity |
| Predicate | discoveryClaimStatus |
P84014
|
FINISHED |
| Object | not reliably confirmed |
—
|
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: not reliably confirmed | Statement: [Themis (disputed Jovian moon), discoveryClaimStatus, not reliably confirmed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryClaimStatus Context triple: [Themis (disputed Jovian moon), discoveryClaimStatus, not reliably confirmed]
-
A.
discoveryClaim
Indicates that an entity asserts having discovered or first identified another entity, concept, or phenomenon.
-
B.
statusOfClaim
chosen
Indicates the current state or condition of a specific claim within a process or system.
-
C.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
D.
claimedStatusOf
Indicates that one entity asserts or declares a particular status or condition about another entity (often itself).
-
E.
hasClaimOn
Indicates that one entity holds a right, entitlement, or demand over another entity or its resources.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:09 p.m.