Triple
T30751742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Báb |
E782972
|
entity |
| Predicate | professionBeforeReligiousMission |
P172185
|
FINISHED |
| Object | merchant |
—
|
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: merchant | Statement: [Báb, professionBeforeReligiousMission, merchant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionBeforeReligiousMission Context triple: [Báb, professionBeforeReligiousMission, merchant]
-
A.
professionBeforeMonasticLife
Indicates the occupation or professional role a person held prior to entering monastic life.
-
B.
declaredReligiousMission
Indicates that an entity has formally stated or proclaimed a specific religious purpose, mission, or objective.
-
C.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
-
D.
religiousAndSpiritualRole
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
-
E.
tookReligiousMissionBreak
Indicates that an entity temporarily paused their usual activities to undertake a religious mission or service.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 8:39 p.m.