Triple
T28669539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryjane |
E725672
|
entity |
| Predicate | countryOfWorkOriginContext |
P129719
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Maryjane, countryOfWorkOriginContext, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfWorkOriginContext Context triple: [Maryjane, countryOfWorkOriginContext, United States]
-
A.
associatedWorkCountryOfOrigin
chosen
Indicates that the related work originates from, or is primarily associated with, a specified country.
-
B.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
C.
placeOfOriginOfWork
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
-
D.
appearsInWorkCountryOfOrigin
Indicates that an entity appears in a work whose country of origin is the specified country.
-
E.
basedOnWorkCountryOfOrigin
Indicates that something is determined or derived from the country of origin of a work.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 28, 2026, 5:03 a.m.