Triple
T24683560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sevel platform |
E611215
|
entity |
| Predicate | basedOnJointVentureBetween |
P102305
|
FINISHED |
| Object | PSA Group |
—
|
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: PSA Group | Statement: [Sevel platform, basedOnJointVentureBetween, PSA Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnJointVentureBetween Context triple: [Sevel platform, basedOnJointVentureBetween, PSA Group]
-
A.
hasJointVenture
Indicates that two or more entities are engaged together in a formally established joint business venture or collaborative commercial undertaking.
-
B.
hasJointVenturePartner
chosen
Indicates that an entity is engaged in a joint venture relationship with another entity as a formal business partner.
-
C.
formerJointVentureWith
Indicates that two entities were previously engaged together in a joint venture relationship that has since ended.
-
D.
requiresForJointVentures
Indicates that one entity sets conditions or prerequisites that must be met by another entity in order to establish or participate in joint ventures.
-
E.
subsidiaryOrJointVenture
Indicates that one organization is either a subsidiary of, or a jointly owned venture with, another organization.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:16 a.m.