Triple
T326693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Economic Community |
E6534
|
entity |
| Predicate | treatySigned |
P596
|
FINISHED |
| Object | 25 March 1957 |
—
|
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: 25 March 1957 | Statement: [European Economic Community, treatySigned, 25 March 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatySigned Context triple: [European Economic Community, treatySigned, 25 March 1957]
-
A.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
B.
treaty
chosen
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
C.
treatySignedPlace
Indicates the location where a treaty was formally signed or concluded.
-
D.
cededByTreaty
Indicates that control or ownership of one entity was formally transferred to another entity as a result of a treaty or formal agreement.
-
E.
treatyAlsoKnownAs
Indicates that a treaty is referred to by an alternative name or alias.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea974d8481908c7d84f72a7728b6 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.