Triple
T5259294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Furnival |
E118781
|
entity |
| Predicate | hasPersonalLife |
P62561
|
FINISHED |
| Object | complex |
—
|
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: complex | Statement: [Mr. Furnival, hasPersonalLife, complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPersonalLife Context triple: [Mr. Furnival, hasPersonalLife, complex]
-
A.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
B.
followsLifeOf
Indicates that one entity’s narrative, development, or progression is tracked or depicted over the course of that entity’s life.
-
C.
hasPerson
Indicates that an entity is associated with or includes a specific person.
-
D.
partnerInLifeEvent
Indicates that two or more entities share a partnership or joint involvement in a specific life event or milestone.
-
E.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.