Triple
T8610879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PBAP |
E203909
|
entity |
| Predicate | operatesBetweenRoles |
P8685
|
FINISHED |
| Object | PBAP client |
—
|
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: PBAP client | Statement: [PBAP, operatesBetweenRoles, PBAP client]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBetweenRoles Context triple: [PBAP, operatesBetweenRoles, PBAP client]
-
A.
operatesBetween
chosen
Indicates a relationship where an action, process, or influence functions or takes effect in the space, interval, or context separating two entities.
-
B.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
C.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
D.
connectsRole
Indicates a relationship in which one entity is linked to another by assigning or associating a specific role between them.
-
E.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ee96ac8190809817c403da2889 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.