Triple
T9335199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippolytus |
E224624
|
entity |
| Predicate | hasSurvivingText |
P87573
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Hippolytus, hasSurvivingText, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingText Context triple: [Hippolytus, hasSurvivingText, Yes]
-
A.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
B.
hasSurvivors
Indicates that one or more entities continue to exist or remain alive after a particular event, condition, or incident.
-
C.
hasTextBy
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
D.
hasNoText
Indicates that the referenced entity or element contains no textual content.
-
E.
hasSurvivorTerm
Indicates that an entity is associated with a term or label specifically used to describe survivors of an event, condition, or circumstance.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37f031888190a90d263d225d163c |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:39 p.m.