Triple
T14793042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The True Law of Free Monarchies |
E347703
|
entity |
| Predicate | writtenByPosition |
P29381
|
FINISHED |
| Object | reigning 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: reigning monarch | Statement: [The True Law of Free Monarchies, writtenByPosition, reigning monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByPosition Context triple: [The True Law of Free Monarchies, writtenByPosition, reigning monarch]
-
A.
writtenByPositionHolder
chosen
Indicates that something (such as a document, statement, or work) is authored or created by a person in their capacity as the holder of a specific position or office.
-
B.
positionOfAuthor
Indicates the spatial or organizational location associated with an author in relation to some reference context.
-
C.
writtenAtLocation
Indicates that an act of writing occurred at a specific physical or geographical location.
-
D.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
E.
writtenByFormer
Indicates that something was written by an individual who previously held a particular role, position, or status.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5ec43c8190ad7a10a556519bb0 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.