Triple
T27771229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | jing |
E701750
|
entity |
| Predicate | roleInNeidan |
P194239
|
FINISHED |
| Object | basis of physical vitality |
—
|
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: basis of physical vitality | Statement: [jing, roleInNeidan, basis of physical vitality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInNeidan Context triple: [jing, roleInNeidan, basis of physical vitality]
-
A.
roleInTaoism
Indicates the specific function, status, or position an entity holds within the beliefs, practices, or institutional structure of Taoism.
-
B.
roleInKonkokyo
Indicates the specific position, office, or function an entity holds within the Konkokyo religious organization.
-
C.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
D.
roleInCobraKai
Indicates that an entity has a specific role or position within the context of Cobra Kai.
-
E.
roleInNobleEightfoldPath
Indicates the specific function or contribution that something has within the structure or practice of the Noble Eightfold Path.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 27, 2026, 4:35 p.m.