Triple
T32877308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1313 Mockingbird Lane |
E840962
|
entity |
| Predicate | inUniverseStreetName |
P181688
|
FINISHED |
| Object | Mockingbird Lane |
—
|
NE NERFINISHED |
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: Mockingbird Lane | Statement: [1313 Mockingbird Lane, inUniverseStreetName, Mockingbird Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseStreetName Context triple: [1313 Mockingbird Lane, inUniverseStreetName, Mockingbird Lane]
-
A.
isCommonStreetNameIn
Indicates that a given name is frequently used as a street name within a specified geographic area or jurisdiction.
-
B.
hasStreetNameLanguage
Indicates that the language in which a street name is expressed is specified.
-
C.
namedAfterStreet
Indicates that an entity’s name is derived from or taken in honor of a particular street.
-
D.
isKeyThoroughfareIn
Indicates that a thoroughfare (such as a road or route) serves as a primary or major access way within a specified area or region.
-
E.
hasHeadquartersOnStreet
Indicates that an organization’s headquarters is located on a specific street.
- 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.