Triple
T28972239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nall |
E734304
|
entity |
| Predicate | localizedBy |
P83356
|
FINISHED |
| Object | Working Designs |
—
|
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: Working Designs | Statement: [Nall, localizedBy, Working Designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localizedBy Context triple: [Nall, localizedBy, Working Designs]
-
A.
localizationBy
chosen
Indicates a relationship where one entity determines, specifies, or constrains the spatial or contextual location of another entity.
-
B.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
-
C.
localization
Indicates the spatial or contextual placement of one entity relative to another or within a specific environment.
-
D.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
E.
laterLocalizedTo
Indicates that an event, condition, or entity that was initially widespread or undefined in scope subsequently became confined or restricted to a specific, localized area or context.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 9:06 a.m.