Triple
T27227408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronan |
E682053
|
entity |
| Predicate | recoveredArtifacts |
P109141
|
FINISHED |
| Object | personal belongings of crew |
—
|
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: personal belongings of crew | Statement: [Kronan, recoveredArtifacts, personal belongings of crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoveredArtifacts Context triple: [Kronan, recoveredArtifacts, personal belongings of crew]
-
A.
recoveredIn
Indicates that something lost, damaged, or impaired has been restored or regained within a particular context, process, or location.
-
B.
discoveredArtifact
Indicates that an entity has found or uncovered a previously unknown or hidden artifact.
-
C.
debrisRecovered
chosen
Indicates that debris resulting from an event or incident has been successfully located, collected, and retrieved.
-
D.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
E.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 9:45 a.m.