Triple
T34173918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guyenne |
E876614
|
entity |
| Predicate | endOfEnglishRule |
P162801
|
FINISHED |
| Object | 1453 |
—
|
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: 1453 | Statement: [Guyenne, endOfEnglishRule, 1453]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfEnglishRule Context triple: [Guyenne, endOfEnglishRule, 1453]
-
A.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
B.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
C.
outcomeForEnglish
chosen
Indicates the result, consequence, or status specifically associated with something in the context of English (e.g., English language, subject, or setting).
-
D.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
E.
reasonForEndOfRule
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:54 a.m.