Triple
T3315519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Egg |
E69671
|
entity |
| Predicate | hasResidentsType |
P5947
|
FINISHED |
| Object | established wealthy families |
—
|
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: established wealthy families | Statement: [East Egg, hasResidentsType, established wealthy families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResidentsType Context triple: [East Egg, hasResidentsType, established wealthy families]
-
A.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
B.
hasTribalCitizens
Indicates that one or more individuals are recognized as official members or citizens of a particular tribe.
-
C.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
D.
hasPopulationType
chosen
Indicates that an entity’s population is classified according to a specific type or category (e.g., demographic, biological, or statistical grouping).
-
E.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb110b28081909b366623e3b0783d |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.