Triple
T16728735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōtō Zen |
E406529
|
entity |
| Predicate | koanUse |
P101867
|
FINISHED |
| Object | limited and indirect |
—
|
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: limited and indirect | Statement: [Sōtō Zen, koanUse, limited and indirect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: koanUse Context triple: [Sōtō Zen, koanUse, limited and indirect]
-
A.
kōanFunction
chosen
Indicates a relationship where something serves as or performs the role or function of a kōan, typically provoking reflection or insight beyond conventional reasoning.
-
B.
numberOfKoans
Indicates the quantity or count of koans associated with a given entity or context.
-
C.
hasNotableKoan
Indicates that an entity is associated with a particularly significant or well-known koan.
-
D.
hasNumberOfKoans
Indicates the relationship that specifies how many koans are associated with or contained by a given entity.
-
E.
kokudaka
Indicates a relationship where a landholding or domain is assigned a value based on its assessed agricultural productivity or tax yield, typically measured in koku.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38749baa48190892b2e2b978f6eb6 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.