Triple
T3352924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katonah, New York |
E70537
|
entity |
| Predicate | developmentCharacter |
P47421
|
FINISHED |
| Object | primarily residential |
—
|
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: primarily residential | Statement: [Katonah, New York, developmentCharacter, primarily residential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentCharacter Context triple: [Katonah, New York, developmentCharacter, primarily residential]
-
A.
developedByCharacter
Indicates that something (such as an item, technique, or work) was created, designed, or brought into existence by a particular character.
-
B.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
C.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
D.
characterDescription
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
E.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb23ec53881908a04c7f784fe8c43 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:13 p.m.