Triple
T30792269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroni |
E784127
|
entity |
| Predicate | appearanceYearTradition |
P31438
|
FINISHED |
| Object | 1823 |
—
|
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: 1823 | Statement: [Moroni, appearanceYearTradition, 1823]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearanceYearTradition Context triple: [Moroni, appearanceYearTradition, 1823]
-
A.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
B.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
C.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
D.
traditionAt
Indicates that a particular tradition is practiced, observed, or associated at a specific place or location.
-
E.
traditionAssociatesWith
Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:42 p.m.