Triple
T35466933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio Delgado |
E1025099
|
entity |
| Predicate | branch of law practiced |
P80389
|
FINISHED |
| Object | 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: civil law | Statement: [Antonio Delgado, branch of law practiced, civil law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branch of law practiced Context triple: [Antonio Delgado, branch of law practiced, civil law]
-
A.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
B.
practicedLawIn
Indicates that a person engaged in the professional practice of law within a specified jurisdiction or location.
-
C.
legalPractice
chosen
Indicates a relationship where an entity engages in or is associated with the professional provision of legal services or the practice of law.
-
D.
legalSystemSpecialization
Indicates that a legal system is specialized or tailored to address a particular domain, issue, or type of case within the broader legal framework.
-
E.
appliesToFieldOfLaw
Indicates that something is relevant or applicable to a particular field or branch 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.