Triple
T8535686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule XXI |
E202071
|
entity |
| Predicate | centuryFormulated |
P31849
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Rule XXI, centuryFormulated, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryFormulated Context triple: [Rule XXI, centuryFormulated, 17th century]
-
A.
formulatedInCentury
Indicates that something (such as an idea, theory, or work) was originally created or developed during a specified century.
-
B.
historicalFormulationCentury
chosen
Indicates the century during which something was originally formulated or first established.
-
C.
formedInCentury
Indicates that an entity (such as an organization, group, or structure) was established or came into existence during a specified century.
-
D.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a295c88190a432a060ee73f04e |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.