Triple
T37277035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-1 |
E924673
|
entity |
| Predicate | appliesToTerminus |
P200780
|
FINISHED |
| Object | Kabaty |
—
|
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: Kabaty | Statement: [A-1, appliesToTerminus, Kabaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToTerminus Context triple: [A-1, appliesToTerminus, Kabaty]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
isTerminusAccessFor
Indicates that one location or facility serves as an access point or terminal endpoint for another transportation route, service, or system.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
associatedWithTerminal
Indicates that one entity has a defined relationship or linkage to a specific terminal or endpoint within a system or structure.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
| PDg | Predicate description generation | batch_69ffac34c5948190be36de5781d91da3 |
completed | May 9, 2026, 9:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.