Triple
T18518894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Actor Prepares |
E452533
|
entity |
| Predicate | inPublicationType |
P218
|
FINISHED |
| Object |
—
|
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: print | Statement: [An Actor Prepares, inPublicationType, print]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inPublicationType Context triple: [An Actor Prepares, inPublicationType, print]
-
A.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
B.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
C.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
-
D.
involvesPublication
Indicates that an action, event, or process includes or is associated with a specific publication as a relevant component.
-
E.
isAcademicPublicationOf
Indicates that one entity is an academic publication (e.g., paper, article, or report) that has been produced by or is associated with 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338be20c8190bc7fe8de050345a2 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.