Triple

T31775853
Position Surface form Disambiguated ID Type / Status
Subject Romanian law E811060 entity
Predicate hasCode P9567 FINISHED
Object Romanian Civil Code
The Romanian Civil Code is the fundamental legal framework governing private law relationships, including contracts, property, family, and obligations, in Romania.
E1977706 NE 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: Romanian Civil Code | Statement: [Romanian law, hasCode, Romanian Civil Code]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Romanian Civil Code
Triple: [Romanian law, hasCode, Romanian Civil Code]
Generated description
The Romanian Civil Code is the fundamental legal framework governing private law relationships, including contracts, property, family, and obligations, in Romania.

Provenance (5 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_69f6abe15d5c81909ccf4ce37f78bc43 completed May 3, 2026, 1:58 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2d9d543d3881909e683468ba168186 completed June 13, 2026, 6:11 p.m.
NEDg Description generation batch_6a2d9f96ca3081909f81be6d5c063c8e completed June 13, 2026, 6:21 p.m.
NED2 Entity disambiguation (via description) batch_6a2da00bad0c81908db156bae068f677 completed June 13, 2026, 6:23 p.m.
Created at: April 30, 2026, 11:35 p.m.