Triple
T31371969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSP |
E800186
|
entity |
| Predicate | codeForLine |
P172551
|
FINISHED |
| Object | Frankfurt U1 |
—
|
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: Frankfurt U1 | Statement: [FSP, codeForLine, Frankfurt U1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeForLine Context triple: [FSP, codeForLine, Frankfurt U1]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
codeForLanguage
Indicates that a piece of code is written in, or intended to be executed by, a particular programming or markup language.
-
C.
lineNumberOrCode
Indicates the specific line number or code identifier associated with an element, reference, or occurrence within a structured sequence or document.
-
D.
codeForSystem
Indicates that something serves as the code, identifier, or encoding used within or by a particular system.
-
E.
usesLineCode
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
- F. None of above. chosen
Provenance (4 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 9:18 p.m.