Triple
T25854286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Centre II |
E651298
|
entity |
| Predicate | isConstituentUnitOf |
P28620
|
FINISHED |
| Object | Faculty of Law, University of Delhi |
—
|
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: Faculty of Law, University of Delhi | Statement: [Law Centre II, isConstituentUnitOf, Faculty of Law, University of Delhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConstituentUnitOf Context triple: [Law Centre II, isConstituentUnitOf, Faculty of Law, University of Delhi]
-
A.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
B.
constitutedBy
Indicates that something is made up of, composed from, or formed by the specified parts or elements.
-
C.
typicalSubunitOf
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
D.
deJurePartOf
Indicates that one entity is legally or formally recognized as a constituent part or subdivision of another entity, according to official rules or law.
-
E.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 7:59 a.m.