Triple
T7039865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR-O06 |
E163481
|
entity |
| Predicate | hasLineCodePrefix |
P66954
|
FINISHED |
| Object | JR-O |
—
|
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: JR-O | Statement: [JR-O06, hasLineCodePrefix, JR-O]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLineCodePrefix Context triple: [JR-O06, hasLineCodePrefix, JR-O]
-
A.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
B.
hasLineNumber
Indicates that something is associated with a specific line number, typically denoting its position within an ordered sequence such as lines of text or code.
-
C.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
D.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
E.
hasCodeIn
Indicates that one entity is represented, defined, or implemented within the codebase or coding context of another entity.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:36 p.m.