Triple
T7966428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaolin Monastery |
E185217
|
entity |
| Predicate | currentAbbotStartYear |
P80049
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Shaolin Monastery, currentAbbotStartYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentAbbotStartYear Context triple: [Shaolin Monastery, currentAbbotStartYear, 1999]
-
A.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
-
B.
currentIncumbentStartYear
Indicates the year in which the entity’s current incumbent began their tenure or term in that role.
-
C.
currentPatriarchStartYear
Indicates the calendar year in which the tenure of the current patriarch officially began.
-
D.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
E.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ba262208190887169fe94e47b0e |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:13 p.m.