Triple
T17589567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibn al-Nafis |
E428407
|
entity |
| Predicate | rejectedClaimOf |
P438
|
FINISHED |
| Object | Galen’s invisible pores in the interventricular septum |
—
|
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: Galen’s invisible pores in the interventricular septum | Statement: [Ibn al-Nafis, rejectedClaimOf, Galen’s invisible pores in the interventricular septum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rejectedClaimOf Context triple: [Ibn al-Nafis, rejectedClaimOf, Galen’s invisible pores in the interventricular septum]
-
A.
rejectedClaim
Indicates that one party has refused to accept, approve, or validate a claim made by another party.
-
B.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
C.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
rejectedAward
Indicates that an entity refused to accept or declined an award that was offered or granted to it.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469e62d5c81909134e30a6d0f2e20 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.