Triple
T11743283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Troy Book |
E279206
|
entity |
| Predicate | commissionedWhen |
P6782
|
FINISHED |
| Object | as Prince of Wales |
—
|
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: as Prince of Wales | Statement: [The Troy Book, commissionedWhen, as Prince of Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissionedWhen Context triple: [The Troy Book, commissionedWhen, as Prince of Wales]
-
A.
commissionedAt
chosen
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
B.
commissionedAfter
Indicates that one entity was formally authorized, ordered, or initiated at a later time than another entity.
-
C.
commissionedDuring
Indicates that an entity was formally authorized, ordered, or initiated within a specified time period or event.
-
D.
commissioned
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
-
E.
commissionedWith
Indicates that one entity was created, produced, or initiated as part of the same commissioning event or request as another entity.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.