Triple
T13131630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Hawi |
E311977
|
entity |
| Predicate | compilesKnowledgeFrom |
P75536
|
FINISHED |
| Object | Greco-Roman medical sources |
—
|
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: Greco-Roman medical sources | Statement: [Al-Hawi, compilesKnowledgeFrom, Greco-Roman medical sources]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilesKnowledgeFrom Context triple: [Al-Hawi, compilesKnowledgeFrom, Greco-Roman medical sources]
-
A.
compilesWorkOf
Indicates that one entity gathers, edits, or assembles the works created by another entity into a collection or compilation.
-
B.
collectionCompiler
chosen
Indicates that an entity is responsible for compiling, assembling, or building a collection from its constituent elements or sources.
-
C.
usesKnowledgeOf
Indicates that one entity applies or draws upon the knowledge possessed by another entity in performing an action or achieving a result.
-
D.
isCompilationOf
Indicates that one entity is a collected or assembled version made up of multiple other entities.
-
E.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b27a8c81909a92ab7be5d3a7e9 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:08 p.m.