Triple
T36598669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addai (pseudonymous authorship) |
E902864
|
entity |
| Predicate | regionOfTraditionalActivity |
P88079
|
FINISHED |
| Object | Edessa |
—
|
NE NERFINISHED |
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: Edessa | Statement: [Addai (pseudonymous authorship), regionOfTraditionalActivity, Edessa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfTraditionalActivity Context triple: [Addai (pseudonymous authorship), regionOfTraditionalActivity, Edessa]
-
A.
traditionalLifestyleRegion
Indicates that a region is characterized by or associated with a traditional lifestyle or way of living.
-
B.
locatedInTraditionalRegion
chosen
Indicates that an entity is situated within a specific traditional or historically recognized region.
-
C.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
D.
traditionallyInvolvedIn
Indicates that an entity has historically or customarily participated in, practiced, or been associated with a particular activity, role, or domain.
-
E.
typicalRegionType
Indicates that a region is of a characteristic or commonly occurring type for a given context or entity.
- 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_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:11 p.m.