Triple
T2557714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fatal Englishman |
E56766
|
entity |
| Predicate | numberOfBiographicalSubjects |
P4086
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [The Fatal Englishman, numberOfBiographicalSubjects, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBiographicalSubjects Context triple: [The Fatal Englishman, numberOfBiographicalSubjects, 3]
-
A.
includesBiographiesOf
Indicates that one entity contains or features biographical information about another entity.
-
B.
numberOfCommemoratedPersons
chosen
Indicates the count of distinct persons who are commemorated or honored in a given context or entity.
-
C.
hasPartInBiography
Indicates that a person or entity is featured or plays a role within someone’s biographical account.
-
D.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
-
E.
notableWorkSubject
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0caeb488190b0dd8e48d0f2777d |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.