Triple
T30859429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine Weaver |
E786017
|
entity |
| Predicate | hasChildInCoverIdentity |
P193418
|
FINISHED |
| Object | Savannah Weaver |
—
|
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: Savannah Weaver | Statement: [Catherine Weaver, hasChildInCoverIdentity, Savannah Weaver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChildInCoverIdentity Context triple: [Catherine Weaver, hasChildInCoverIdentity, Savannah Weaver]
-
A.
hasSiblingInCover
Indicates that one entity has a sibling who appears together with it on the same cover (e.g., book, album, or publication cover).
-
B.
hasRelativeInCover
Indicates that an entity has a relative who is currently in hiding, undercover, or otherwise concealed.
-
C.
hasAuthorityOnCover
Indicates that one entity holds decision-making or control authority over the content, design, or use of another entity’s cover (e.g., a document, publication, or product).
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
containsCoverOf
Indicates that one entity includes within it a cover or covering representation of 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: April 29, 2026, 8:46 p.m.