Triple
T28671704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periochae |
E725736
|
entity |
| Predicate | relationshipToLivy |
P202120
|
FINISHED |
| Object | epitomizes each book of Ab Urbe Condita |
—
|
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: epitomizes each book of Ab Urbe Condita | Statement: [Periochae, relationshipToLivy, epitomizes each book of Ab Urbe Condita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToLivy Context triple: [Periochae, relationshipToLivy, epitomizes each book of Ab Urbe Condita]
-
A.
relationshipToEva
Indicates a specified type of personal or social relationship that an entity has with Eva.
-
B.
relationshipToUser
Indicates the type of connection or association an entity has with the current user.
-
C.
relationshipToPuntila
Indicates the type or nature of a relationship that an entity has to Puntila.
-
D.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
E.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
| PDg | Predicate description generation | batch_6a005326c1508190ace47b84c08b9565 |
completed | May 10, 2026, 9:43 a.m. |
Created at: April 28, 2026, 5:04 a.m.