Triple
T33355077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul |
E854049
|
entity |
| Predicate | appearsInWorkForm |
P194375
|
FINISHED |
| Object | two-act play |
—
|
LITERAL 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: two-act play | Statement: [Paul, appearsInWorkForm, two-act play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInWorkForm Context triple: [Paul, appearsInWorkForm, two-act play]
-
A.
basedInWorkForm
Indicates that an entity operates or is situated within a particular work-related format, structure, or organizational form.
-
B.
appearsInSectionOfWork
Indicates that one entity is contained within or shows up in a specific section or part of a larger work.
-
C.
appearsInWorkSetIn
Indicates that an entity appears in a creative work whose narrative or setting takes place in a specified location or context.
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
appearsInWorkAbout
Indicates that an entity is mentioned or featured within a work whose subject or focus is that 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 1, 2026, 1:34 a.m.