Triple
T624908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerald Holtom |
E14594
|
entity |
| Predicate | hasWorkUsedBy |
P17842
|
FINISHED |
| Object | peace movement worldwide |
—
|
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: peace movement worldwide | Statement: [Gerald Holtom, hasWorkUsedBy, peace movement worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkUsedBy Context triple: [Gerald Holtom, hasWorkUsedBy, peace movement worldwide]
-
A.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
B.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
-
C.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
D.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
-
E.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e43002c81908e0c7dab29b75978 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49e2107548190af0c1d67cfa475d1 |
completed | March 1, 2026, 8:14 p.m. |
Created at: March 1, 2026, 7:35 p.m.