Triple
T26438454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graduate Center Library |
E665016
|
entity |
| Predicate | hasComputersForUsers |
P19443
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Graduate Center Library, hasComputersForUsers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComputersForUsers Context triple: [Graduate Center Library, hasComputersForUsers, yes]
-
A.
hasComputerWorkstations
chosen
Indicates that an entity is equipped with or provides access to computer workstations.
-
B.
hasUsers
Indicates that an entity is associated with one or more users who use, own, or are linked to it.
-
C.
usedInComputerFamily
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
-
D.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
E.
hasProductUser
Indicates that a product is associated with or used by a particular user.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 26, 2026, 11:56 p.m.