Triple
T25188045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha Kingston |
E630777
|
entity |
| Predicate | triesToSave |
P158010
|
FINISHED |
| Object | Juliet Sykes |
—
|
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: Juliet Sykes | Statement: [Samantha Kingston, triesToSave, Juliet Sykes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triesToSave Context triple: [Samantha Kingston, triesToSave, Juliet Sykes]
-
A.
triesToTake
Indicates an attempt by one entity to take possession or control of another entity or resource, regardless of whether the attempt succeeds.
-
B.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
C.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
D.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
-
E.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e0bbd2c8190a30a70dcf5523875 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:44 p.m.