Triple
T13956129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthodox churches |
E335665
|
entity |
| Predicate | sharesTradition |
P11721
|
FINISHED |
| Object | Eastern Christian tradition |
—
|
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: Eastern Christian tradition | Statement: [Orthodox churches, sharesTradition, Eastern Christian tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesTradition Context triple: [Orthodox churches, sharesTradition, Eastern Christian tradition]
-
A.
sharesTraditionsWith
chosen
Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
-
B.
sharesDesignTraditionWith
Indicates that two entities originate from or participate in the same design tradition, sharing common stylistic principles, methods, or heritage.
-
C.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
D.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
E.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e78a4a481908e438745631a43c0 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.