Triple
T440301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ado Annie Carnes |
E10098
|
entity |
| Predicate | themeAssociatedWith |
P7707
|
FINISHED |
| Object | romantic indecision |
—
|
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: romantic indecision | Statement: [Ado Annie Carnes, themeAssociatedWith, romantic indecision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeAssociatedWith Context triple: [Ado Annie Carnes, themeAssociatedWith, romantic indecision]
-
A.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
B.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
themeExamples
chosen
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
D.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
E.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.