Triple
T31775825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian law |
E811060
|
entity |
| Predicate | mainSourceOfLaw |
P65906
|
FINISHED |
| Object | Constitution of Romania |
—
|
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: Constitution of Romania | Statement: [Romanian law, mainSourceOfLaw, Constitution of Romania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSourceOfLaw Context triple: [Romanian law, mainSourceOfLaw, Constitution of Romania]
-
A.
majorLegalSource
chosen
Indicates that one entity serves as a primary or authoritative legal basis or reference for another entity.
-
B.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
C.
legislationSource
Indicates that one entity serves as the originating authority, basis, or source for a particular piece of legislation or legal rule.
-
D.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
-
E.
governsBodyOfLaw
Indicates that one entity has authoritative control over the creation, interpretation, or enforcement of a particular body of law.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 30, 2026, 11:35 p.m.