Triple
T379650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curly McLain |
E8649
|
entity |
| Predicate | hasFictionalResidence |
P7550
|
FINISHED |
| Object | a ranch near Laurey Williams's farm |
—
|
LITERAL 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: a ranch near Laurey Williams's farm | Statement: [Curly McLain, hasFictionalResidence, a ranch near Laurey Williams's farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalResidence Context triple: [Curly McLain, hasFictionalResidence, a ranch near Laurey Williams's farm]
-
A.
fictionalResidence
chosen
Indicates that one entity is the place where another entity lives or is based within a fictional or imaginary context.
-
B.
formerResidenceOf
Indicates that a location was once the place where a person or entity lived or was based, but is no longer their current residence.
-
C.
isHomeOf
Indicates that a place serves as the primary residence or base for a person, group, or organization.
-
D.
servedAsResidenceOf
Indicates that something functioned as the home or dwelling place of a particular person or group.
-
E.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.