Triple
T18589456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 112 Ocean Avenue house |
E454323
|
entity |
| Predicate | hasCurrentAddress |
P4379
|
FINISHED |
| Object | 108 Ocean Avenue |
—
|
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: 108 Ocean Avenue | Statement: [112 Ocean Avenue house, hasCurrentAddress, 108 Ocean Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentAddress Context triple: [112 Ocean Avenue house, hasCurrentAddress, 108 Ocean Avenue]
-
A.
hasAddress
chosen
Indicates that an entity is associated with a specific address or location.
-
B.
hasAddressState
Indicates that an entity’s address is located within a particular state or state-level administrative region.
-
C.
hasFictionalAddressStatus
Indicates that an entity’s address is designated as fictional rather than a real-world, verifiable location.
-
D.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
E.
hasPostalAddressComponent
Indicates that an entity is associated with a specific part or element of a postal address (such as street, city, or postal code).
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b4a2a0819098047ee81278bd9d |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.