Triple
T828005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Assent |
E17898
|
entity |
| Predicate | historicallyGivenIn |
P20047
|
FINISHED |
| Object | person by the monarch |
—
|
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: person by the monarch | Statement: [Royal Assent, historicallyGivenIn, person by the monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyGivenIn Context triple: [Royal Assent, historicallyGivenIn, person by the monarch]
-
A.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
B.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
C.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
D.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
E.
historicallySoughtAs
Indicates that one entity has been pursued, desired, or actively sought by another entity over a historical period or in past contexts.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab99b1e48190afad1f073348b29a |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa79a6488190a634388e071ed9b7 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4781c88190ae36906251347cdc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.