Triple
T24259017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex civilis Helveticae |
E604648
|
entity |
| Predicate | isFundamentalBodyOf |
P33647
|
FINISHED |
| Object | Swiss private 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: Swiss private law | Statement: [Codex civilis Helveticae, isFundamentalBodyOf, Swiss private law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFundamentalBodyOf Context triple: [Codex civilis Helveticae, isFundamentalBodyOf, Swiss private law]
-
A.
isFundamental
Indicates that something is a basic, essential, or foundational element upon which other things depend or are built.
-
B.
sovereignBodyOf
Indicates that one entity is the supreme governing authority or ruling body over another entity, such as a territory, organization, or people.
-
C.
isStandingBodyOf
Indicates that one entity is positioned upright and stationary in close physical proximity to another entity.
-
D.
isKeyBodyOf
chosen
Indicates that one entity serves as the primary or central body/content component of another entity.
-
E.
isTechnicalBodyOf
Indicates that one entity serves as the specialized or technical governing, advisory, or decision-making body for 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6592688190a9c6850a2e979858 |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.