Triple
T33030677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holiday |
E845154
|
entity |
| Predicate | employedContributor |
P16029
|
FINISHED |
| Object | James Michener |
—
|
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: James Michener | Statement: [Holiday, employedContributor, James Michener]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedContributor Context triple: [Holiday, employedContributor, James Michener]
-
A.
employedWriter
Indicates that a writer is formally employed by a person, organization, or entity to perform writing-related work.
-
B.
creativeContributor
Indicates a relationship where an entity plays an active role in originating, designing, or shaping the creative content or form of another entity.
-
C.
employedComposer
Indicates that one entity (such as a person or organization) employs another entity in the role of a composer.
-
D.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
-
E.
contributors
chosen
Indicates that one or more entities have provided work, resources, or input toward the creation, development, or maintenance of another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:24 a.m.