Triple
T3300713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R11 |
E69323
|
entity |
| Predicate | associatedWithServices |
P2830
|
FINISHED |
| Object | 4 train |
—
|
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: 4 train | Statement: [R11, associatedWithServices, 4 train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithServices Context triple: [R11, associatedWithServices, 4 train]
-
A.
relatedService
Indicates that one service is connected or associated with another service in a relevant or dependent way.
-
B.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
associatedWithSee
Indicates a relationship where one entity is contextually or functionally linked to another through the act or concept of seeing or visual observation.
-
D.
originallyAssociatedWith
Indicates that an entity was first linked, connected, or affiliated with another entity before any later changes in association.
-
E.
serviceWith
Indicates that one entity provides or is associated with a particular service offered to or used 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a7d224819080d9a638e08bb8a8 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.