Triple
T34446807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Line Agreement |
E884251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cartel agreement |
C22463
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cartel agreement Context triple: [Red Line Agreement, instanceOf, cartel agreement]
-
A.
antitrust agreement
chosen
An antitrust agreement is a formal or informal arrangement between two or more independent economic entities that coordinates their competitive behavior in a way that may restrict competition, such as fixing prices, limiting output, or dividing markets.
-
B.
business cartel
A business cartel is a group of independent companies that secretly or explicitly collude to control prices, limit competition, or manipulate markets for mutual benefit.
-
C.
association agreement
An association agreement is a formal contract that defines the rights, responsibilities, and collaborative arrangements between two or more parties forming an ongoing relationship, often within a professional, organizational, or international context.
-
D.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
E.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
- F. None of above.
Provenance (1 batch)
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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.