Triple
T4455961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schiedam Gate |
E97722
|
entity |
| Predicate | accessProvidedTo |
P51771
|
FINISHED |
| Object | route toward Schiedam |
—
|
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: route toward Schiedam | Statement: [Schiedam Gate, accessProvidedTo, route toward Schiedam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessProvidedTo Context triple: [Schiedam Gate, accessProvidedTo, route toward Schiedam]
-
A.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
B.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
C.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
D.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3564216b081908c41109100b36862 |
completed | March 13, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.