Triple
T127047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatican civil law |
E2572
|
entity |
| Predicate | historicallyIncorporated |
P4534
|
FINISHED |
| Object | selected provisions of Italian civil 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: selected provisions of Italian civil law | Statement: [Vatican civil law, historicallyIncorporated, selected provisions of Italian civil law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyIncorporated Context triple: [Vatican civil law, historicallyIncorporated, selected provisions of Italian civil law]
-
A.
incorporatedAsTownIn
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
foundedAfter
Indicates that one entity was founded at a later time than another entity.
-
D.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
E.
incorporatedThrough
chosen
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25761e9248190a7205bfc36cb5c45 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.