Triple
T35772554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond Babbitt |
E1034202
|
entity |
| Predicate | careFacility |
P101666
|
FINISHED |
| Object | Wallbrook |
—
|
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: Wallbrook | Statement: [Raymond Babbitt, careFacility, Wallbrook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: careFacility Context triple: [Raymond Babbitt, careFacility, Wallbrook]
-
A.
agingFacility
Indicates that a facility is undergoing or associated with the process of aging, deterioration, or decline in condition over time.
-
B.
homeFacilityName
Indicates the name of the primary facility or location that serves as the entity’s designated home base.
-
C.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
-
D.
formerHomeFacility
Indicates that an entity was previously housed, based, or operated in a particular facility but no longer is.
-
E.
homeFacilityUse
chosen
Indicates that an entity uses or is served by a particular home or primary facility as its main location for activities or services.
- 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_69f76e14a1e081908eddd57bd6fdb3be |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1f927d08190bd236e0afb3d2bcb |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.