Triple
T37872507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shado-Pan Monastery |
E944639
|
entity |
| Predicate | primaryLoreFocus |
P97516
|
FINISHED |
| Object | Shado-Pan order |
E2229357
|
NE 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: Shado-Pan order | Statement: [Shado-Pan Monastery, primaryLoreFocus, Shado-Pan order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLoreFocus Context triple: [Shado-Pan Monastery, primaryLoreFocus, Shado-Pan order]
-
A.
primaryFunctionInLore
chosen
Indicates that something’s main role or purpose is defined within a fictional or narrative lore context.
-
B.
loreTrait
Indicates that an entity possesses a specific lore-related characteristic or attribute within a fictional or narrative context.
-
C.
primaryInfluence
Indicates that one entity serves as the main or most significant influencing factor on another entity’s state, behavior, or outcome.
-
D.
primaryCult
Indicates that an entity serves as the main or most significant object of religious worship or veneration for another entity.
-
E.
lore
Indicates that information, stories, or knowledge about something is being told, recorded, or associated with it as part of a larger narrative or tradition.
- F. None of above.
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4154246ebc8190a457e244f272e4fa |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.