Triple
T1317397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adly Mansour |
E28135
|
entity |
| Predicate | legalSpecialization |
P6403
|
FINISHED |
| Object | constitutional 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: constitutional law | Statement: [Adly Mansour, legalSpecialization, constitutional law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalSpecialization Context triple: [Adly Mansour, legalSpecialization, constitutional law]
-
A.
practicedLawIn
Indicates that a person engaged in the professional practice of law within a specified jurisdiction or location.
-
B.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
C.
branchOfLaw
chosen
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
D.
legalRepresentation
Indicates that one entity formally acts on behalf of another in legal matters, such as providing counsel, advocacy, or defense within a legal system.
-
E.
legalBackground
Indicates that an entity has education, training, or experience related to law or the legal profession.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c175079481909077cf11ed72d6fa |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beebcb348190964bd7215811942c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.