Triple
T3290459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Cullen |
E69086
|
entity |
| Predicate | formerHumanStatus |
P30469
|
FINISHED |
| Object | Spanish influenza patient |
—
|
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: Spanish influenza patient | Statement: [Edward Cullen, formerHumanStatus, Spanish influenza patient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerHumanStatus Context triple: [Edward Cullen, formerHumanStatus, Spanish influenza patient]
-
A.
formerUser
Indicates that an entity was previously a user of another entity or system but is no longer one.
-
B.
formerGround
Indicates that an entity previously served as the ground or base for another entity but no longer holds that role.
-
C.
formerState
chosen
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
-
D.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
E.
formerName
Indicates that an entity was previously known by a different name in the past.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb05bd6b08190bcb9f0e5da82bc21 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.