Triple
T27715209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor ham |
E698796
|
entity |
| Predicate | inventedIn |
P162971
|
FINISHED |
| Object | New Jersey |
—
|
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: New Jersey | Statement: [Taylor ham, inventedIn, New Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inventedIn Context triple: [Taylor ham, inventedIn, New Jersey]
-
A.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
B.
inventedDuring
Indicates that an invention or concept was created or first developed within a specified time period or historical era.
-
C.
wasInventedInYear
Indicates that an entity was created or invented in a specific calendar year.
-
D.
basedOnInventionOf
Indicates that something is derived from, developed using, or fundamentally relies on a particular invention.
-
E.
usedInventionOf
Indicates that one entity made use of, applied, or implemented the invention created by another entity.
- F. None of above. chosen
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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635cfa6088190aae92d408c036238 |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 3:04 p.m.