Triple
T8222400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunfleet Sands |
E192094
|
entity |
| Predicate | hasApproximateHouseholdSupply |
P81705
|
FINISHED |
| Object | over 100000 homes |
—
|
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: over 100000 homes | Statement: [Gunfleet Sands, hasApproximateHouseholdSupply, over 100000 homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateHouseholdSupply Context triple: [Gunfleet Sands, hasApproximateHouseholdSupply, over 100000 homes]
-
A.
isHouseholdStaple
Indicates that something is commonly and consistently kept on hand in a household as a basic, regularly used item.
-
B.
hasHouseholdFeature
Indicates that a household possesses or includes a specific feature, attribute, or amenity.
-
C.
hasHouseholdType
Indicates the type or category of household associated with an entity (e.g., family, single-person, shared, etc.).
-
D.
requiresHouse
Indicates that one entity depends on or needs a house (or housing) in order for a condition, action, or relationship to be fulfilled.
-
E.
hasNumberOfHouses
Indicates the quantity of houses associated with a given entity.
- F. None of above. chosen
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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb77cae2948190ae4507b75b5d5784 |
completed | March 31, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36af41e081909dee92b9bc4947f1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4d9b03108190a6785834f21ff75e |
completed | March 31, 2026, 4:29 a.m. |
Created at: March 30, 2026, 5:45 p.m.