Triple
T17887855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speed Force |
E447240
|
entity |
| Predicate | canBeEnteredBy |
P31837
|
FINISHED |
| Object | speedsters |
—
|
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: speedsters | Statement: [Speed Force, canBeEnteredBy, speedsters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeEnteredBy Context triple: [Speed Force, canBeEnteredBy, speedsters]
-
A.
mayEnter
chosen
Indicates that one entity is permitted or authorized to enter or access another entity or location.
-
B.
hasEntranceRole
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
C.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
-
D.
hasEntranceControl
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
E.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c14c4348190bb77712d9eae1d51 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.