Triple
T36235020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace Darling |
E891353
|
entity |
| Predicate | partnerInRescue |
P185716
|
FINISHED |
| Object | William Darling |
E2175391
|
NE 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: William Darling | Statement: [Grace Darling, partnerInRescue, William Darling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInRescue Context triple: [Grace Darling, partnerInRescue, William Darling]
-
A.
partnerInMission
Indicates that two or more entities collaborate as partners in carrying out the same mission or operation.
-
B.
partnerInRestoration
Indicates that two or more entities collaborate as partners in a restoration effort or project.
-
C.
partnerInPursuit
Indicates that two or more entities are collaborating or jointly engaged in the same pursuit, goal, or endeavor.
-
D.
partnerInDangerFrom
Indicates that one partner is exposed to danger, threat, or harm originating from the other partner.
-
E.
roleInRescue
Indicates the specific function or responsibility an entity has within a rescue operation or event.
- F. None of above. chosen
Provenance (5 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a30dbee4819097c0358dd20f471a |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.