Triple
T13308932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Falaise |
E317009
|
entity |
| Predicate | establishedOverlordshipOf |
P70686
|
FINISHED |
| Object | King of England |
—
|
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: King of England | Statement: [Treaty of Falaise, establishedOverlordshipOf, King of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedOverlordshipOf Context triple: [Treaty of Falaise, establishedOverlordshipOf, King of England]
-
A.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
B.
establishedAsSignoria
Indicates that an entity was instituted or set up as a signoria, i.e., a governing lordship or ruling authority over a city or territory.
-
C.
hasSovereignPowerOver
chosen
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
D.
conqueredByRuler
Indicates that a place, people, or entity was taken over and brought under control through force or domination by a specific ruler.
-
E.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.