Triple
T6519494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NISO |
E148344
|
entity |
| Predicate | hasStandard |
P1371
|
FINISHED |
| Object | Z39.50 |
E27528
|
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: Z39.50 | Statement: [NISO, hasStandard, Z39.50]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Z39.50 Context triple: [NISO, hasStandard, Z39.50]
-
A.
Z39.50
chosen
Z39.50 is a client-server protocol used primarily by libraries and information services to search and retrieve bibliographic and related data from remote databases in a standardized way.
-
B.
BNF bibliographic database
The BNF bibliographic database is the comprehensive online catalog of the Bibliothèque nationale de France, providing detailed bibliographic records for its collections of books, manuscripts, and other documents.
-
C.
MARC
MARC is a regional planning and coordination agency serving the Kansas City metropolitan area, focusing on transportation, emergency services, environmental planning, and community development.
-
D.
MARC
MARC is a commuter rail service in Maryland that connects Washington, D.C. with Baltimore and other regional destinations.
-
E.
MARC standards
MARC standards are a set of bibliographic data formats used worldwide to structure and exchange library catalog information in a consistent, machine-readable way.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac11d0e481908103c4b51de9521e |
completed | March 27, 2026, 4:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6d51af5308190928c97ceb5d5fa2d |
completed | March 27, 2026, 7:06 p.m. |
Created at: March 27, 2026, 1:45 p.m.