Triple
T2591364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 5, 1948 |
E58127
|
entity |
| Predicate | hasCatalogStatus |
P10583
|
FINISHED |
| Object | well-documented work by Jackson Pollock |
—
|
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: well-documented work by Jackson Pollock | Statement: [No. 5, 1948, hasCatalogStatus, well-documented work by Jackson Pollock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogStatus Context triple: [No. 5, 1948, hasCatalogStatus, well-documented work by Jackson Pollock]
-
A.
catalogueStatus
chosen
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
B.
hasOnlineCatalog
Indicates that an entity provides a catalog of its items or offerings that is accessible via the internet.
-
C.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
hasUnitStatus
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
E.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd40075f08190b760cb41c1417169 |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.