Triple
T11955338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LuEsther T. Mertz Library |
E284536
|
entity |
| Predicate | hasResearchCollections |
P102458
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LuEsther T. Mertz Library, hasResearchCollections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchCollections Context triple: [LuEsther T. Mertz Library, hasResearchCollections, true]
-
A.
hasSpecialCollections
Indicates that an entity possesses or maintains distinct, curated collections that are set apart from its general holdings.
-
B.
hasResearchActivities
Indicates that an entity engages in, conducts, or is associated with research-related activities.
-
C.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
D.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
-
E.
hasResearchArm
Indicates that an entity includes or is associated with a specific research-focused component, group, or division.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.