Triple
T35378489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internationale Handelsgesellschaft |
E1022579
|
entity |
| Predicate | citesProvision |
P43606
|
FINISHED |
| Object | EEC Treaty |
—
|
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: EEC Treaty | Statement: [Internationale Handelsgesellschaft, citesProvision, EEC Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citesProvision Context triple: [Internationale Handelsgesellschaft, citesProvision, EEC Treaty]
-
A.
citesBody
chosen
Indicates that one entity references or cites the content, findings, or text of another entity as a source.
-
B.
legalCitationSystem
Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
-
C.
citesConstitutionalProvision
Indicates that one legal document, decision, or argument explicitly references and relies on a specific provision of a constitution.
-
D.
citesEdition
Indicates that one work references or acknowledges a specific edition of another work as its source.
-
E.
citationAct
Indicates an act in which one entity cites, references, or otherwise acknowledges another entity as a source or authority.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.