Triple
T6335813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S41 |
E142487
|
entity |
| Predicate | lineNumberingSystem |
P3378
|
FINISHED |
| Object | Berlin S-Bahn line numbering |
—
|
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: Berlin S-Bahn line numbering | Statement: [S41, lineNumberingSystem, Berlin S-Bahn line numbering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineNumberingSystem Context triple: [S41, lineNumberingSystem, Berlin S-Bahn line numbering]
-
A.
lineNumberingIntroduced
Indicates that a system, document, or text has had line numbering initiated or enabled.
-
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.
numberingType
chosen
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
D.
standardNumberingScheme
Indicates that there is a specific, commonly accepted numbering system or convention being applied to identify or order the related entities.
-
E.
includesNumberingRange
Indicates that one entity contains or covers a specified contiguous range of numbers associated with 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_69c008d4d8e88190ad301c05b08722ac |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0654a88a881908d5cb2aa7f22c4c7 |
completed | March 22, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:30 p.m.