Triple
T28889324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rose Dawson Calvert |
E732652
|
entity |
| Predicate | searchesForObject |
P47887
|
FINISHED |
| Object | Heart of the Ocean (necklace) |
—
|
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: Heart of the Ocean (necklace) | Statement: [Old Rose Dawson Calvert, searchesForObject, Heart of the Ocean (necklace)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: searchesForObject Context triple: [Old Rose Dawson Calvert, searchesForObject, Heart of the Ocean (necklace)]
-
A.
searchingFor
chosen
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
B.
usesFoundObject
Indicates that an entity makes use of an object that it has previously found or discovered.
-
C.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
D.
soughtFor
Indicates that one entity is being searched for, pursued, or wanted by another, often for a specific purpose or reason.
-
E.
usedToSearchFor
Indicates that one entity serves as a tool, method, or resource employed to look for, locate, or retrieve 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a744e1c8190bff56db4cb0b68df |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:53 a.m.