Triple
T11393627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shippen family |
E269908
|
entity |
| Predicate | hasFamilyEstateType |
P33508
|
FINISHED |
| Object | urban townhouses |
—
|
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: urban townhouses | Statement: [Shippen family, hasFamilyEstateType, urban townhouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyEstateType Context triple: [Shippen family, hasFamilyEstateType, urban townhouses]
-
A.
hasEstateType
chosen
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
B.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
C.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
D.
hasFamilyArea
Indicates a relationship where an entity possesses or includes a designated area intended for family use or family-related activities.
-
E.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001796f48190822526f52e3f0337 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.