Triple
T37389413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolosse |
E928661
|
entity |
| Predicate | hasWorkTitleMeaning |
P198375
|
FINISHED |
| Object | “dolosse” as concrete sea-defence blocks |
—
|
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: “dolosse” as concrete sea-defence blocks | Statement: [Dolosse, hasWorkTitleMeaning, “dolosse” as concrete sea-defence blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkTitleMeaning Context triple: [Dolosse, hasWorkTitleMeaning, “dolosse” as concrete sea-defence blocks]
-
A.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
B.
hasWorkTitleType
Indicates that an entity holds a specific category or type of work-related title (e.g., job title type or role classification).
-
C.
hasWorkTitleVariant
Indicates that an entity has an alternative or variant form of its work title, such as a different wording, spelling, or language version of the same title.
-
D.
hasWorkingTitle
Indicates that an entity is associated with a provisional or temporary title used during its development or production.
-
E.
hasWorkTitleSource
Indicates that the source or origin of an entity’s work title is specified or referenced.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69fedfd850ec81909b55f90dc850167e |
completed | May 9, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:16 p.m.