Triple
T9168258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayyub |
E220018
|
entity |
| Predicate | testedWith |
P86589
|
FINISHED |
| Object | loss of wealth |
—
|
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: loss of wealth | Statement: [Ayyub, testedWith, loss of wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedWith Context triple: [Ayyub, testedWith, loss of wealth]
-
A.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
B.
testedOn
Indicates that an entity has been used as the subject or material in a test, experiment, or evaluation performed by another entity.
-
C.
testedInCase
Indicates that something (such as a method, component, or behavior) is exercised or verified within a particular test case.
-
D.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
-
E.
isUsedToTest
Indicates that one entity serves as a means or tool for evaluating, examining, or verifying another entity.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaadfb50881909b9127f92e4b3e21 |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:22 p.m.