Triple
T24321189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP25 |
E612966
|
entity |
| Predicate | outwardCode |
P134749
|
FINISHED |
| Object | NP25 |
—
|
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: NP25 | Statement: [NP25, outwardCode, NP25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outwardCode Context triple: [NP25, outwardCode, NP25]
-
A.
outwardCodeIncludes
Indicates that a broader outward postal code area contains or encompasses a specified smaller area or code segment.
-
B.
hasOutwardCode
chosen
Indicates that one entity is associated with a specific outward (first-part) segment of a postal code used for mail routing.
-
C.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
D.
operatorCode
Indicates that one entity is associated with a specific operator’s identifying code used to denote who performs or manages an operation or service.
-
E.
internalCode
Indicates that an entity is associated with an internal identification code used within a specific system or organization.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ac7fc08190993f707f2f97e7f5 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:51 a.m.