Triple
T7154778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Société Anonyme |
E166781
|
entity |
| Predicate | regulationArea |
P63323
|
FINISHED |
| Object | company law |
—
|
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: company law | Statement: [Société Anonyme, regulationArea, company law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulationArea Context triple: [Société Anonyme, regulationArea, company law]
-
A.
regulatesArea
Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
-
B.
regulatedArea
chosen
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
C.
regulatedIn
Indicates that one entity’s activity, expression, or occurrence is controlled, influenced, or modulated by another entity within a specific context or system.
-
D.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
E.
regulatoryField
Indicates that one entity operates within, is governed by, or is associated with a particular area or domain of regulation defined by another entity.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80c747c8190a017a2b1c3e78a3f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.