Triple
T35802007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu al-Ala al-Ma'arri |
E1035000
|
entity |
| Predicate | lostEyesight |
P141489
|
FINISHED |
| Object | in childhood |
—
|
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: in childhood | Statement: [Abu al-Ala al-Ma'arri, lostEyesight, in childhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostEyesight Context triple: [Abu al-Ala al-Ma'arri, lostEyesight, in childhood]
-
A.
blind
chosen
Indicates that an entity lacks the ability to see, either partially or completely, resulting in an absence or severe limitation of visual perception.
-
B.
lost
Indicates that an entity no longer possesses or has been deprived of another entity it previously had.
-
C.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
-
D.
lostOn
Indicates that one entity was defeated by or failed against another entity in a competitive or comparative context.
-
E.
hasSenseImpairment
Indicates that an entity experiences a reduction or loss in one or more sensory abilities (such as sight, hearing, or touch).
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a25aa3e08190a6ce3b03ec020d18 |
completed | May 3, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.