Triple
T21069447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking Dublin: Trial Pieces |
E519063
|
entity |
| Predicate | aboutWorkType |
P86785
|
FINISHED |
| Object | archaeological report |
—
|
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: archaeological report | Statement: [Viking Dublin: Trial Pieces, aboutWorkType, archaeological report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboutWorkType Context triple: [Viking Dublin: Trial Pieces, aboutWorkType, archaeological report]
-
A.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
B.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
C.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
D.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
E.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb6d3a081909d6a6b181786deff |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:46 p.m.