Triple
T17687994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Sherman |
E440944
|
entity |
| Predicate | neighborDescription |
P128576
|
FINISHED |
| Object | beautiful young woman living upstairs |
—
|
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: beautiful young woman living upstairs | Statement: [Richard Sherman, neighborDescription, beautiful young woman living upstairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighborDescription Context triple: [Richard Sherman, neighborDescription, beautiful young woman living upstairs]
-
A.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
B.
neighborhoodCharacteristic
Indicates that a particular characteristic, feature, or quality is associated with or describes a given neighborhood.
-
C.
neighborCharacter
Indicates that one character is located adjacent to or next to another character in a given context.
-
D.
depictsNeighborhood
Indicates that one entity visually represents or portrays the neighborhood or local area associated with another entity.
-
E.
locationDescription
Indicates a textual description that specifies or characterizes the location of an 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704944d8819089b153aa14839fc0 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:03 a.m.