Triple
T32877324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1313 Mockingbird Lane |
E840962
|
entity |
| Predicate | hasFrontYardFeature |
P180456
|
FINISHED |
| Object | overgrown yard |
—
|
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: overgrown yard | Statement: [1313 Mockingbird Lane, hasFrontYardFeature, overgrown yard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrontYardFeature Context triple: [1313 Mockingbird Lane, hasFrontYardFeature, overgrown yard]
-
A.
hasCourtyardFeature
Indicates that a courtyard possesses or includes a specific feature or characteristic.
-
B.
hasPorch
Indicates that one entity (typically a building or residence) includes or is equipped with a porch as part of its structure.
-
C.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
D.
hasPorchLocation
Indicates the spatial location or placement of a porch relative to another referenced entity.
-
E.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: May 1, 2026, 1:18 a.m.