Triple
T7276297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Troyes |
E163037
|
entity |
| Predicate | allied |
P600
|
FINISHED |
| Object | English crown |
—
|
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 crown | Statement: [Treaty of Troyes, allied, English crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allied Context triple: [Treaty of Troyes, allied, English crown]
-
A.
alliedDesignation
Indicates that one entity assigns or recognizes an allied status or designation for another entity.
-
B.
alliedForces
Indicates that multiple entities are cooperating militarily or strategically as part of the same alliance or coalition.
-
C.
alliance
chosen
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
D.
alliedUnit
Indicates that one unit is associated as an ally or cooperative partner with another unit, typically sharing goals or working together.
-
E.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.