Triple
T38550502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Earl Spilner |
E925096
|
entity |
| Predicate | coverStoryResidence |
P75
|
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: [Brian Earl Spilner, coverStoryResidence, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverStoryResidence Context triple: [Brian Earl Spilner, coverStoryResidence, Los Angeles]
-
A.
locationCoverStory
Indicates that a particular location is used as a cover or front to conceal the true nature, purpose, or activities associated with something or someone.
-
B.
residence
chosen
Indicates that one entity lives at, is based in, or habitually occupies the location represented by the other entity.
-
C.
depictsResidence
Indicates that one entity visually represents or portrays the place where another entity lives or resides.
-
D.
residenceContext
Indicates the situational or environmental circumstances under which an entity resides or lives in a particular place.
-
E.
builtResidence
Indicates that one entity constructed or was responsible for constructing a residence for another entity or for itself.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:32 p.m.