Triple
T33188242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucas Pegg |
E849529
|
entity |
| Predicate | hasPrimaryFunctionInStory |
P53895
|
FINISHED |
| Object | drives central narrative |
—
|
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: drives central narrative | Statement: [Lucas Pegg, hasPrimaryFunctionInStory, drives central narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryFunctionInStory Context triple: [Lucas Pegg, hasPrimaryFunctionInStory, drives central narrative]
-
A.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasPrimaryStory
Indicates that one entity is designated as the main or most important story associated with another entity.
-
C.
hasPlannedPrimaryFunction
Indicates that an entity is intended or designed to perform a specified main function or role.
-
D.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
E.
hasMainPlotElement
chosen
Indicates that one entity serves as a central or primary plot element within the narrative of 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a017969ff908190a7a1a46b3f5ae362 |
completed | May 11, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a017609ff4c8190aba8a1864d39a608 |
completed | May 11, 2026, 6:24 a.m. |
Created at: May 1, 2026, 1:29 a.m.