Triple
T30859424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catherine Weaver |
E786017
|
entity |
| Predicate | homeLocationInCoverIdentity |
P170570
|
FINISHED |
| Object | Los Angeles |
—
|
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: Los Angeles | Statement: [Catherine Weaver, homeLocationInCoverIdentity, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeLocationInCoverIdentity Context triple: [Catherine Weaver, homeLocationInCoverIdentity, Los Angeles]
-
A.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
B.
coverLocation
Indicates that one entity serves as a covering or protective layer positioned at or over a specific location of another entity.
-
C.
localIdentity
Indicates that an entity’s identity or role is defined specifically within a particular local context, scope, or environment, rather than globally.
-
D.
nationalityInCoverIdentity
Indicates that an entity’s assumed or cover identity is associated with a particular nationality.
-
E.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
- 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_69f691a7353c8190bf1cf3ead5cc6421 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:46 p.m.