Triple
T36134651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rommely family |
E1045129
|
entity |
| Predicate | centralToCharacter |
P195842
|
FINISHED |
| Object | Francie Nolan |
—
|
NE NERFINISHED |
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: Francie Nolan | Statement: [Rommely family, centralToCharacter, Francie Nolan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToCharacter Context triple: [Rommely family, centralToCharacter, Francie Nolan]
-
A.
centralToCase
Indicates that something plays a pivotal or essential role in determining the outcome or understanding of a particular case.
-
B.
centralToMovement
Indicates that something plays a core, defining, or organizing role within a particular movement or collective effort.
-
C.
transformsCharacterInto
Indicates that one entity causes or undergoes a change that turns a character into another form, state, or identity.
-
D.
regionCharacter
Indicates a characteristic, feature, or quality that typifies or defines a particular region.
-
E.
romanizedCenter
Indicates that one entity is the central or primary romanized (Latin-script) representation associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.