Triple
T5629768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Muwatta |
E147802
|
entity |
| Predicate | transmittedOrally |
P32654
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Al-Muwatta, transmittedOrally, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmittedOrally Context triple: [Al-Muwatta, transmittedOrally, yes]
-
A.
languageOfTransmission
Indicates the language used to convey or transmit the content or information in a given communication or resource.
-
B.
hasRichOralTradition
chosen
Indicates that an entity is associated with a longstanding, culturally significant body of stories, histories, or knowledge transmitted primarily through spoken word rather than written texts.
-
C.
speechTradition
Indicates a relationship where an entity is associated with, follows, or participates in a particular established way or tradition of speaking or oral expression.
-
D.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
E.
hasOralDiscFunction
Indicates that an entity possesses a specific functional role or capability associated with its oral disc.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223c722481908bc3684825b3977a |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.