Triple
T22111835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanh Thai Nguyen |
E546435
|
entity |
| Predicate | episcopalMotto |
P25715
|
FINISHED |
| Object | Communio (Communion) |
—
|
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: Communio (Communion) | Statement: [Thanh Thai Nguyen, episcopalMotto, Communio (Communion)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: episcopalMotto Context triple: [Thanh Thai Nguyen, episcopalMotto, Communio (Communion)]
-
A.
scripturalMotto
Indicates that one entity serves as the official scriptural or religiously inspired motto or guiding phrase associated with another entity.
-
B.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
mottoOrInsigniaTheme
Indicates that a motto or insignia is based on, refers to, or thematically centers around a particular concept, idea, or subject.
-
E.
mottoEmphasizes
chosen
Indicates that a motto highlights, stresses, or gives special importance to a particular idea, value, or theme.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12949cc7881908898ca7dc130f57f |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.