Triple
T23727898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice |
E586329
|
entity |
| Predicate | issuedWork |
P153729
|
FINISHED |
| Object | Strategikon (attributed) |
—
|
NE NERFINISHED |
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: Strategikon (attributed) | Statement: [Maurice, issuedWork, Strategikon (attributed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedWork Context triple: [Maurice, issuedWork, Strategikon (attributed)]
-
A.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
-
B.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
C.
issuedAct
Indicates that an authority formally created, enacted, or put into effect a specific act, order, or legal instrument.
-
D.
wonWork
Indicates that one party has successfully secured or been awarded a particular job, contract, or work opportunity over others.
-
E.
issuedWithin
Indicates that one entity (such as a document, license, or order) was formally created, granted, or released during a specified time period or within a defined temporal boundary.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9167bdc81909d837e018e7d0e29 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:08 p.m.