Triple
T3050257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Working Drafts |
E83548
|
entity |
| Predicate | hasStageAfter |
P24493
|
FINISHED |
| Object | Candidate Recommendation |
—
|
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: Candidate Recommendation | Statement: [Working Drafts, hasStageAfter, Candidate Recommendation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageAfter Context triple: [Working Drafts, hasStageAfter, Candidate Recommendation]
-
A.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
B.
hasStep
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
C.
hasSubsequentStandard
chosen
Indicates that one standard is followed or superseded by another standard that comes after it in sequence or version.
-
D.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
E.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.