Triple
T4264166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Matthew |
E96182
|
entity |
| Predicate | reasonForPseudonym |
P7885
|
FINISHED |
| Object | religious persecution risk in 16th-century England |
—
|
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: religious persecution risk in 16th-century England | Statement: [Thomas Matthew, reasonForPseudonym, religious persecution risk in 16th-century England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForPseudonym Context triple: [Thomas Matthew, reasonForPseudonym, religious persecution risk in 16th-century England]
-
A.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
C.
reasonForName
chosen
Indicates the explanation or cause behind why an entity has a particular name.
-
D.
pseudonymInspiredBy
Indicates that a pseudonym was chosen or created based on, or in homage to, another name, person, work, or concept.
-
E.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fc94f64819091f438d8ae5ed687 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.