Triple
T28637558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mia Form |
E724828
|
entity |
| Predicate | hasPrimaryRoleIn |
P14496
|
FINISHED |
| Object | main plot |
—
|
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: main plot | Statement: [Mia Form, hasPrimaryRoleIn, main plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryRoleIn Context triple: [Mia Form, hasPrimaryRoleIn, main plot]
-
A.
hasMainRole
chosen
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
B.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
C.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
D.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
E.
hasSubjectRoleIn
Indicates that an entity serves in a specific subject role within a particular context, situation, or relationship.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: April 28, 2026, 4:41 a.m.