Triple
T34514183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish National Monument |
E886103
|
entity |
| Predicate | requiresForWorks |
P14667
|
FINISHED |
| Object | ministerial consent |
—
|
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: ministerial consent | Statement: [Irish National Monument, requiresForWorks, ministerial consent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresForWorks Context triple: [Irish National Monument, requiresForWorks, ministerial consent]
-
A.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
B.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
workRequirement
chosen
Indicates that one entity imposes or specifies a condition related to work that another entity must fulfill.
-
E.
requiresParticipationOf
Indicates that one entity’s occurrence, validity, or completion depends on the active involvement or participation of 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 2:01 a.m.