Triple
T29020725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 742 Evergreen Terrace |
E737444
|
entity |
| Predicate | hasPostalCodeInSomeEpisodes |
P32512
|
FINISHED |
| Object | 49007 |
—
|
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: 49007 | Statement: [742 Evergreen Terrace, hasPostalCodeInSomeEpisodes, 49007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalCodeInSomeEpisodes Context triple: [742 Evergreen Terrace, hasPostalCodeInSomeEpisodes, 49007]
-
A.
hasPostalRole
Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
-
B.
hasPostalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
C.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
-
D.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
E.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 9:49 a.m.