Triple
T25667791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Themisto |
E643571
|
entity |
| Predicate | lostAfterDiscovery |
P158968
|
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: [Themisto, lostAfterDiscovery, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostAfterDiscovery Context triple: [Themisto, lostAfterDiscovery, true]
-
A.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
B.
lostAt
Indicates that an entity ceased to be in possession of or unable to be found at a specific location or context.
-
C.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
D.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
E.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:08 p.m.