Triple
T37053067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Walker Lindh |
E917099
|
entity |
| Predicate | convertedToReligionDate |
P28896
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [John Walker Lindh, convertedToReligionDate, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToReligionDate Context triple: [John Walker Lindh, convertedToReligionDate, 1990s]
-
A.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
B.
religiousConversionPeriod
chosen
Indicates the time span during which an entity undergoes or is involved in a process of religious conversion.
-
C.
convertedToIslamWith
Indicates that one entity adopted Islam through the influence, guidance, or involvement of another entity.
-
D.
dateOfChristianization
Indicates the date on which a person, group, or place was converted to Christianity or formally adopted the Christian faith.
-
E.
dateOfConversion
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.