Triple
T21130121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Medicine Society |
E520662
|
entity |
| Predicate | transmitsKnowledgeThrough |
P40656
|
FINISHED |
| Object | oral tradition |
—
|
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: oral tradition | Statement: [Grand Medicine Society, transmitsKnowledgeThrough, oral tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmitsKnowledgeThrough Context triple: [Grand Medicine Society, transmitsKnowledgeThrough, oral tradition]
-
A.
knowledgeExchange
Indicates a reciprocal sharing or transfer of knowledge, information, or expertise between entities.
-
B.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
C.
teachesAbout
Indicates that one entity provides instruction or information to another entity on a particular subject or topic.
-
D.
taughtThrough
chosen
Indicates that one entity provided instruction, education, or training to another entity by means of a specified method, medium, or intermediary.
-
E.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723556ec08190a2ade96c76f9cec7 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.