Triple
T20976914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Πολύβιος |
E516650
|
entity |
| Predicate | mainWorkBooksPlanned |
P142325
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Πολύβιος, mainWorkBooksPlanned, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkBooksPlanned Context triple: [Πολύβιος, mainWorkBooksPlanned, 40]
-
A.
plannedToDisplayWork
Indicates that an entity intended or arranged in advance to exhibit or present a work.
-
B.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba4a0dc819083b90795d26adfff |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:47 p.m.