Triple
T28363989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry-Castañeda Library |
E718435
|
entity |
| Predicate | hasMapCollection |
P426
|
FINISHED |
| Object | Perry-Castañeda Library Map Collection |
E718435
|
NE 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: Perry-Castañeda Library Map Collection | Statement: [Perry-Castañeda Library, hasMapCollection, Perry-Castañeda Library Map Collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapCollection Context triple: [Perry-Castañeda Library, hasMapCollection, Perry-Castañeda Library Map Collection]
-
A.
hasMapStructure
Indicates that one entity is organized or represented according to the structural layout or schema defined by another (map-like) entity.
-
B.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
-
C.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
D.
hasMapReference
Indicates that an entity is associated with a specific map or map location reference.
-
E.
hasCollection
chosen
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
- F. None of above.
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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1627cf64788190960d88f9988d43b4 |
completed | May 26, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 28, 2026, 12:53 a.m.