Triple
T19863311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meleager of Gadara |
E477323
|
entity |
| Predicate | hasSurvivingWorkCountApprox |
P34532
|
FINISHED |
| Object | over 130 epigrams |
—
|
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: over 130 epigrams | Statement: [Meleager of Gadara, hasSurvivingWorkCountApprox, over 130 epigrams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurvivingWorkCountApprox Context triple: [Meleager of Gadara, hasSurvivingWorkCountApprox, over 130 epigrams]
-
A.
hasWorkCount
chosen
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
B.
hasSurvivingElement
Indicates that an entity retains at least one remaining or extant part, instance, or component that still exists.
-
C.
hasSubsequentWork
Indicates that one work is followed by another work that continues, succeeds, or builds upon it in sequence.
-
D.
hasComponentWork
Indicates that one work includes another work as a constituent or subordinate component within it.
-
E.
hasWorker
Indicates that one entity employs, utilizes, or is associated with another entity in the role of a worker.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589c4c0081908cd51ff75441e7ac |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.