Triple
T26796787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RKV (MARC) |
E670974
|
entity |
| Predicate | usedForLine |
P98
|
FINISHED |
| Object | MARC Brunswick Line |
—
|
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: MARC Brunswick Line | Statement: [RKV (MARC), usedForLine, MARC Brunswick Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForLine Context triple: [RKV (MARC), usedForLine, MARC Brunswick Line]
-
A.
usedByLine
Indicates that something (such as a resource, tool, or component) is utilized or operated by a particular line (for example, a production line, transit line, or code line).
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
D.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
E.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 4:20 a.m.