Triple
T33429492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pencil Monument |
E856085
|
entity |
| Predicate | commemoratesConflictBetween |
P11046
|
FINISHED |
| Object | Scots |
—
|
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: Scots | Statement: [Pencil Monument, commemoratesConflictBetween, Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemoratesConflictBetween Context triple: [Pencil Monument, commemoratesConflictBetween, Scots]
-
A.
commemoratesConflict
chosen
Indicates a relationship where something (such as a monument, event, or work) serves to remember, honor, or mark a specific conflict or war.
-
B.
commemoratesAlliance
Indicates a relationship where one entity honors or marks the memory of an alliance formed between two or more parties.
-
C.
commemoratesField
Indicates that one entity serves to honor, remember, or mark the significance of another entity, event, or achievement.
-
D.
partOfHistoricalConflict
Indicates that one entity participated in, belonged to, or was involved as a component of a larger historical conflict or war.
-
E.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:36 a.m.