Triple
T2810197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faculty of Social Sciences |
E54148
|
entity |
| Predicate | locatedInInstitutionType |
P43727
|
FINISHED |
| Object | college |
—
|
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: college | Statement: [Faculty of Social Sciences, locatedInInstitutionType, college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInInstitutionType Context triple: [Faculty of Social Sciences, locatedInInstitutionType, college]
-
A.
hasLocalInstitution
Indicates that a given place or region possesses or hosts an institution that operates locally within its boundaries.
-
B.
usedByInstitutionType
Indicates that something (such as a resource, tool, or service) is utilized or employed by a particular type or category of institution.
-
C.
usedByInstitution
Indicates that something (such as a resource, tool, or method) is utilized or employed by an institution.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
involvesInstitution
Indicates that an action, event, or relationship includes or is associated with an institution as a participating party.
- F. None of above. chosen
Provenance (4 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde335b38819090c70d5e2ca14d79 |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:59 p.m.