Triple
T37736772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joshu’s Mu |
E940297
|
entity |
| Predicate | associatedMaster |
P204367
|
FINISHED |
| Object | Zhaozhou Congshen |
E283030
|
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: Zhaozhou Congshen | Statement: [Joshu’s Mu, associatedMaster, Zhaozhou Congshen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMaster Context triple: [Joshu’s Mu, associatedMaster, Zhaozhou Congshen]
-
A.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
B.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
C.
associatedSingle
Indicates a one-to-one association where an entity is linked to exactly one corresponding related entity.
-
D.
associatedStable
Indicates that one entity is linked or connected to a particular stable in a way that denotes an ongoing or defined association.
-
E.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
- F. None of above. chosen
Provenance (5 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41040c8eb88190a244f9242ae52c3e |
completed | June 28, 2026, 11:22 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.