Triple
T33271562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | co-founding the literary magazine Yugen |
E851786
|
entity |
| Predicate | involvedRoleOf |
P184599
|
FINISHED |
| Object | editor |
—
|
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: editor | Statement: [co-founding the literary magazine Yugen, involvedRoleOf, editor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedRoleOf Context triple: [co-founding the literary magazine Yugen, involvedRoleOf, editor]
-
A.
involvesPartyRole
chosen
Indicates that a situation, event, or agreement includes a participant fulfilling a specific role or function within that context.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
involvedActor
Indicates that an entity participates as an actor or participant in the referenced event, activity, or situation.
-
D.
roleInActs
Indicates the specific function or character that an entity performs or portrays within one or more acts or performances.
-
E.
holdersPlayedRoleIn
Indicates that the holders of something (e.g., a position, title, or asset) participated in or contributed to a particular role within an event, activity, or context.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 1, 2026, 1:32 a.m.