Triple
T36598668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addai (pseudonymous authorship) |
E902864
|
entity |
| Predicate | timeOfTraditionalSetting |
P120199
|
FINISHED |
| Object | early Christian period |
—
|
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: early Christian period | Statement: [Addai (pseudonymous authorship), timeOfTraditionalSetting, early Christian period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfTraditionalSetting Context triple: [Addai (pseudonymous authorship), timeOfTraditionalSetting, early Christian period]
-
A.
timeInTradition
chosen
Indicates the temporal context or period in which a given tradition is practiced, observed, or relevant.
-
B.
timeOfSetting
Indicates the specific time at which an event, object, or phenomenon is set, scheduled, or takes place.
-
C.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
D.
traditionDuration
Indicates the length of time for which a particular tradition has been practiced or observed.
-
E.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 3, 2026, 4:11 p.m.