Triple
T13599185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Jacson |
E324898
|
entity |
| Predicate | coverStoryElement |
P68011
|
FINISHED |
| Object | businessman |
—
|
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: businessman | Statement: [Frank Jacson, coverStoryElement, businessman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverStoryElement Context triple: [Frank Jacson, coverStoryElement, businessman]
-
A.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
-
B.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
C.
featuredElement
chosen
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
headOfStoryOn
Indicates that one entity serves as the main headline or leading title for a story that appears on another entity (such as a page or section).
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0795acc8190a08667ab9dcb0d44 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.