Triple
T3675833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Copperfield |
E77988
|
entity |
| Predicate | followsCharacterTo |
P49434
|
FINISHED |
| Object | maturity |
—
|
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: maturity | Statement: [David Copperfield, followsCharacterTo, maturity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsCharacterTo Context triple: [David Copperfield, followsCharacterTo, maturity]
-
A.
followsCharacter
Indicates that one character moves or acts after another character, maintaining a trailing or subsequent position or sequence relative to them.
-
B.
followsCharactersFrom
Indicates that one entity continues or tracks the narrative, actions, or developments involving specific characters from another entity.
-
C.
followsCharacterOccupation
Indicates that one character’s occupation or job role comes after or succeeds another character’s occupation in a sequence or progression.
-
D.
followsLetter
Indicates that one element in a sequence comes immediately after another element in alphabetical or ordered letter arrangement.
-
E.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc462ffdc8190896e9f98f648e2f3 |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e59bec81908b58e753fcb862b4 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:25 p.m.