Triple
T9659083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old York Library collection on New York City history |
E233540
|
entity |
| Predicate | curationStatus |
P89456
|
FINISHED |
| Object | extensive |
—
|
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: extensive | Statement: [Old York Library collection on New York City history, curationStatus, extensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curationStatus Context triple: [Old York Library collection on New York City history, curationStatus, extensive]
-
A.
collectingStatus
Indicates the current state or phase of an ongoing collection process or activity.
-
B.
catalogueStatus
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
C.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
-
D.
cultStatus
Indicates that something has achieved a devoted, niche following or admiration that is disproportionate to its mainstream popularity.
-
E.
categoryStatus
Indicates the current state or condition assigned to a category within a given system or context.
- 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_69ca848c1ba88190b84b410cd14627fc |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9bdfc3b08190835e86ff99663214 |
completed | April 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:14 p.m.