Triple
T4366906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schools of the University of Cambridge |
E98796
|
entity |
| Predicate | subordinateUnits |
P28620
|
FINISHED |
| Object | faculties |
—
|
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: faculties | Statement: [Schools of the University of Cambridge, subordinateUnits, faculties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subordinateUnits Context triple: [Schools of the University of Cambridge, subordinateUnits, faculties]
-
A.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
B.
subunitOf
chosen
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
C.
formerSubunit
Indicates that one entity was previously a subunit or subordinate part of another entity, but no longer holds that status.
-
D.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
E.
notableSubordinateFormation
Indicates that one formation is a significant or distinguished subordinate unit within the organizational structure of another formation.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35201be7081908808e81634060f95 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.