Triple
T7154012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paréage of 1278 |
E166762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paréage agreement |
C17881
|
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: paréage agreement Context triple: [Paréage of 1278, instanceOf, paréage agreement]
-
A.
partnership agreement
chosen
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
B.
parvorder
A parvorder is a taxonomic rank in biological classification below infraorder and above superfamily, grouping closely related organisms within an order.
-
C.
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.
-
D.
naming agreement
A naming agreement is a legal contract in which one party grants another the right to use a specific name (such as a personal, brand, or facility name) under defined terms and conditions.
-
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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:46 p.m.