Triple
T30680304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negotiable Order of Withdrawal account |
E781033
|
entity |
| Predicate | firstIntroducedInRegion |
P76642
|
FINISHED |
| Object | New England |
E333
|
NE 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: New England | Statement: [Negotiable Order of Withdrawal account, firstIntroducedInRegion, New England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedInRegion Context triple: [Negotiable Order of Withdrawal account, firstIntroducedInRegion, New England]
-
A.
introducedInGameRegion
Indicates that something first appeared or was made available within a specific region of a game.
-
B.
developedInRegion
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
C.
introducedToRegion
chosen
Indicates that an entity was brought or made present in a particular geographic or administrative region for the first time or as a new occurrence.
-
D.
firstForRegion
Indicates that something is the earliest or primary instance of its kind within a specified region.
-
E.
foundingRegion
Indicates the geographic region where an entity (such as an organization, movement, or institution) was originally founded.
- F. None of above.
Provenance (4 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870ecce7c8190b417e4f1b523a657 |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
Created at: April 29, 2026, 8:32 p.m.