Triple
T37521028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imlac |
E932772
|
entity |
| Predicate | comparesLifeTo |
P278
|
FINISHED |
| Object | a state of trial |
—
|
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: a state of trial | Statement: [Imlac, comparesLifeTo, a state of trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesLifeTo Context triple: [Imlac, comparesLifeTo, a state of trial]
-
A.
comparesHumanBeingsTo
Indicates a relationship where one entity evaluates or contrasts human beings with another entity or group based on some shared or differing characteristics.
-
B.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
C.
dividesLifeInto
Indicates partitioning or organizing a life or lifespan into distinct segments, phases, or periods.
-
D.
publicLife
Indicates that an entity is involved in activities, roles, or interactions that are conducted openly in the public sphere rather than in private life.
-
E.
averageLifespanComparedTo
Indicates how the typical lifespan of one entity compares in length to that of another entity.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:17 p.m.