Triple
T13308937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Falaise |
E317009
|
entity |
| Predicate | requiredGarrisonsBy |
P74496
|
FINISHED |
| Object | English troops |
—
|
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: English troops | Statement: [Treaty of Falaise, requiredGarrisonsBy, English troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredGarrisonsBy Context triple: [Treaty of Falaise, requiredGarrisonsBy, English troops]
-
A.
garrisonSize
Indicates the number of troops or defenders stationed at a particular location as its garrison.
-
B.
requiresForDefense
chosen
Indicates that one entity must have or obtain another entity as a necessary condition to provide or maintain defense.
-
C.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
D.
garrisonUseUntil
Indicates that a garrison occupies or utilizes a location or resource up to a specified end time or condition.
-
E.
garrisonTown
Indicates that a town serves as a military base or station where armed forces are permanently or regularly housed.
- 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.