Triple
T7155174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean cataloging rules |
E166789
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | KORMARC format |
E27070
|
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: KORMARC format | Statement: [Korean cataloging rules, relatedTo, KORMARC format]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KORMARC format Context triple: [Korean cataloging rules, relatedTo, KORMARC format]
-
A.
KORMARC
chosen
KORMARC is the Korean implementation of the MARC bibliographic data format standard used for cataloging and exchanging library records in Korea.
-
B.
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.
-
C.
MARC
MARC is a commuter rail service in Maryland that connects Washington, D.C. with Baltimore and other regional destinations.
-
D.
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.
-
E.
Korean MARC
Korean MARC is a national bibliographic metadata standard used in South Korea for cataloging library and information resources.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80c747c8190a017a2b1c3e78a3f |
completed | March 27, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7adb0ea288190b7eef76de30a3a1e |
completed | March 28, 2026, 10:30 a.m. |
Created at: March 27, 2026, 2:47 p.m.