Triple
T31299546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hookers |
E798175
|
entity |
| Predicate | developedInState |
P9365
|
FINISHED |
| Object | Minnesota |
—
|
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: Minnesota | Statement: [The Hookers, developedInState, Minnesota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInState Context triple: [The Hookers, developedInState, Minnesota]
-
A.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
B.
developedInRegion
chosen
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
C.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
-
D.
seDesarrollaEn
Indicates that an event, process, or activity takes place or unfolds within a specific location, context, or environment.
-
E.
placeOfDevelopment
Indicates the location where something (such as a product, project, or work) was created, designed, or developed.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 9:14 p.m.