Triple
T25966474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next House |
E645683
|
entity |
| Predicate | hasAddressCode |
P45702
|
FINISHED |
| Object | W71 |
—
|
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: W71 | Statement: [Next House, hasAddressCode, W71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddressCode Context triple: [Next House, hasAddressCode, W71]
-
A.
hasAddress
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.
hasPostalAddressSystem
Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
-
D.
hasAreaCode
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
E.
hasPostalAddressComponent
chosen
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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 8:48 a.m.