Triple
T2286571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speer Library (former main library) |
E51403
|
entity |
| Predicate | institutionTypeServed |
P8369
|
FINISHED |
| Object | theological seminary |
—
|
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: theological seminary | Statement: [Speer Library (former main library), institutionTypeServed, theological seminary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: institutionTypeServed Context triple: [Speer Library (former main library), institutionTypeServed, theological seminary]
-
A.
servesInstitution
chosen
Indicates that one entity provides services or functions in support of a particular institution.
-
B.
typeOfInstitution
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
-
C.
eligibleInstitution
Indicates that an institution satisfies specified criteria or requirements to qualify for a particular program, benefit, or status.
-
D.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
E.
operatesInstitution
Indicates that an entity manages and runs the activities or services of an institution.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc24730208190af8a5cf443d334f7 |
completed | March 7, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69abbdbb9e4c819085fc588626ec7c09 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.