Triple
T33657269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ConnectCard |
E862257
|
entity |
| Predicate | currentOperatorName |
P183481
|
FINISHED |
| Object | Pittsburgh Regional Transit |
—
|
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: Pittsburgh Regional Transit | Statement: [ConnectCard, currentOperatorName, Pittsburgh Regional Transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOperatorName Context triple: [ConnectCard, currentOperatorName, Pittsburgh Regional Transit]
-
A.
currentOperators
chosen
Indicates that certain entities are the operators who are presently active or responsible for operating a given system, process, or resource.
-
B.
initialOperator
Indicates that an entity serves as the first or primary operator initiating a process, action, or operation involving another entity.
-
C.
otherOperator
Indicates a relationship where one operator is distinguished from, or serves as an alternative to, another operator within the same context or system.
-
D.
coreOperator
Indicates that an entity functions as a primary or central operator responsible for executing or managing a core operation within a system or process.
-
E.
isOperatorOn
Indicates that one entity serves as an operator responsible for operating, controlling, or managing another entity (such as a system, machine, or process).
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 1:42 a.m.