Triple
T33318362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bobolian |
E853071
|
entity |
| Predicate | knowledge |
P176479
|
FINISHED |
| Object | oral traditions |
—
|
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 traditions | Statement: [bobolian, knowledge, oral traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knowledge Context triple: [bobolian, knowledge, oral traditions]
-
A.
knowledgeType
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
-
B.
knows
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
C.
knowledgeOutput
Indicates that an entity produces, expresses, or makes available knowledge, information, or learned content as an output.
-
D.
knowledgeScope
Indicates the extent or range of information, topics, or understanding that an entity possesses or is concerned with.
-
E.
knowledgeEffect
Indicates the impact or change that possessing or acquiring certain knowledge has on an entity, such as altering its beliefs, capabilities, or behavior.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e312d7fc819094dec41810f2585d |
completed | May 3, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:33 a.m.