Triple
T33478336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte Lucas |
E857386
|
entity |
| Predicate | locatedNearResidence |
P41003
|
FINISHED |
| Object | Longbourn |
E244240
|
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: Longbourn | Statement: [Charlotte Lucas, locatedNearResidence, Longbourn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearResidence Context triple: [Charlotte Lucas, locatedNearResidence, Longbourn]
-
A.
residesNear
chosen
Indicates that one entity lives or is located in close physical proximity to another entity.
-
B.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
C.
centeredAtResidence
Indicates that an entity’s primary focus, activity, or presence is located at a specified residence.
-
D.
locatedNearRegion
Indicates that one entity is situated in close geographic proximity to a specified region.
-
E.
locatedNearAdministrativeEntity
Indicates that one entity is geographically situated close to, or in the immediate vicinity of, an administrative unit such as a city, district, or region.
- F. None of above.
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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366561dab88190b57e3e1f8bea4535 |
completed | June 20, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.