Triple
T376581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostle Paul |
E8385
|
entity |
| Predicate | conversionEvent |
P11797
|
FINISHED |
| Object | experience on the road to Damascus |
—
|
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: experience on the road to Damascus | Statement: [Apostle Paul, conversionEvent, experience on the road to Damascus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionEvent Context triple: [Apostle Paul, conversionEvent, experience on the road to Damascus]
-
A.
convertsTo
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
B.
conversionCompleted
Indicates that a previously initiated conversion process has finished successfully.
-
C.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
D.
convertibility
Indicates the capacity or possibility for one entity, state, or form to be changed or transformed into another.
-
E.
convertsFrom
Indicates that one entity is transformed or changed into another entity, with the source being the starting form or state.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.