Triple
T33265597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Powers in S.S. Wimbledon case |
E851636
|
entity |
| Predicate | concernedTreaty |
P33308
|
FINISHED |
| Object | Treaty of Versailles |
—
|
NE NERFINISHED |
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: Treaty of Versailles | Statement: [Allied Powers in S.S. Wimbledon case, concernedTreaty, Treaty of Versailles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernedTreaty Context triple: [Allied Powers in S.S. Wimbledon case, concernedTreaty, Treaty of Versailles]
-
A.
relatedToTreaty
Indicates that there exists a connection, association, or relevance between an entity and a specific treaty or treaties.
-
B.
treatyFocus
chosen
Indicates that a treaty is primarily concerned with, directed toward, or centered on a particular subject, issue, or area.
-
C.
treatyMention
Indicates that a treaty is referenced or mentioned in relation to the associated entities or context.
-
D.
followedTreaty
Indicates that one party complied with and acted in accordance with the terms of a specified treaty in relation to another party.
-
E.
linkedToTreaty
Indicates that an entity has a formal connection or association with a specific treaty, such as being established by, governed by, or otherwise related to that treaty.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:32 a.m.