Triple
T26195600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RSO SO 4801 |
E655090
|
entity |
| Predicate | originalCatalogNumberFor |
P189415
|
FINISHED |
| Object | 461 Ocean Boulevard |
—
|
NE NERFINISHED |
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: 461 Ocean Boulevard | Statement: [RSO SO 4801, originalCatalogNumberFor, 461 Ocean Boulevard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCatalogNumberFor Context triple: [RSO SO 4801, originalCatalogNumberFor, 461 Ocean Boulevard]
-
A.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
B.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
C.
originalFor
Indicates that one entity serves as the source, basis, or prototype from which another entity is derived, adapted, or created.
-
D.
hasCatalogNumberPrefix
Indicates that an item’s catalog number begins with a specified prefix.
-
E.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 26, 2026, 8:46 p.m.