Triple
T3831395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esperanto movement |
E91018
|
entity |
| Predicate | isNonReligious |
P52242
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Esperanto movement, isNonReligious, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonReligious Context triple: [Esperanto movement, isNonReligious, true]
-
A.
isNonSectarian
Indicates that an organization, institution, or activity is not affiliated with, restricted to, or biased toward any particular religious sect or denomination.
-
B.
excludedReligion
Indicates that a particular religion is explicitly not allowed, accepted, or included within a given context, group, or condition.
-
C.
notWorshippedAs
Indicates that one entity is not regarded, treated, or honored as an object of worship by another entity or group.
-
D.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of another entity.
-
E.
hasReligiousTheme
Indicates that something (such as a work, event, or object) centrally involves or expresses religious ideas, symbols, practices, or narratives.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb86207c81908f40a01fe27f6a0b |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:17 p.m.