Triple
T36086152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Out West |
E1043785
|
entity |
| Predicate | hasNotableProductionContributionBy |
P190652
|
FINISHED |
| Object | WondaGurl |
E82454
|
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: WondaGurl | Statement: [Out West, hasNotableProductionContributionBy, WondaGurl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableProductionContributionBy Context triple: [Out West, hasNotableProductionContributionBy, WondaGurl]
-
A.
hasNotableUncreditedContribution
Indicates that an entity made a significant contribution to another entity or work that is not formally credited or acknowledged.
-
B.
hasProductionCredit
chosen
Indicates that an entity is credited as having contributed to the production of another entity, such as a work, project, or media item.
-
C.
notableProductionFor
Indicates that an entity is especially well-known or recognized for producing or creating another specified entity.
-
D.
hasNotableAwardCreatedBy
Indicates that an award received by an entity was created or established by a specific creator or organization.
-
E.
hasNotableAuthorWork
Indicates that an author is notably associated with creating a particular work.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38ddfb44b88190aedba642e6d337af |
completed | June 22, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.