Triple
T37770960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zen |
E941544
|
entity |
| Predicate | majorJapaneseSchool |
P201756
|
FINISHED |
| Object | Rinzai |
—
|
NE NERFINISHED |
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: Rinzai | Statement: [Zen, majorJapaneseSchool, Rinzai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorJapaneseSchool Context triple: [Zen, majorJapaneseSchool, Rinzai]
-
A.
hasSubschoolsInJapan
Indicates that an entity (such as a school or organization) has subordinate branches or subschools located within Japan.
-
B.
upperCourseJapaneseName
Indicates that an entity has a Japanese name specifically for the upper course (upstream section) of a river.
-
C.
mainJapaneseGateway
Indicates that one entity serves as the primary Japanese access point or entry gateway for another entity.
-
D.
JapaneseMission
Indicates a mission, delegation, or official undertaking that is specifically associated with Japan or originates from Japanese authorities or organizations.
-
E.
JapaneseAdvantage
Indicates that one party holds a comparative advantage or superior position specifically in a Japanese context (e.g., language, market, culture, or environment) relative to another.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
| PDg | Predicate description generation | batch_6a001adbe6588190b7af521508b18898 |
completed | May 10, 2026, 5:42 a.m. |
Created at: May 3, 2026, 4:19 p.m.