Triple
T26692048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-waves |
E672911
|
entity |
| Predicate | cannotTravelThrough |
P119401
|
FINISHED |
| Object | vacuum |
—
|
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: vacuum | Statement: [P-waves, cannotTravelThrough, vacuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotTravelThrough Context triple: [P-waves, cannotTravelThrough, vacuum]
-
A.
allowsTravelAcross
Indicates that one entity enables or permits movement or passage from one side or location to another across a separating space or boundary.
-
B.
transportRestriction
Indicates that there are limitations, prohibitions, or special conditions governing the use of a particular mode or means of transportation between entities.
-
C.
timeTravelConstraint
Indicates a restriction or rule governing when, how, or under what conditions time travel between different points in time is allowed or possible.
-
D.
cannotBeCrossedBy
chosen
Indicates that one entity forms a barrier or obstacle that another entity is unable to pass through or traverse.
-
E.
hasTourismRestriction
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:26 a.m.